Hoe het platform en het Power Apps-product echt werken — de beslissingen, de afwegingen en de dingen die lastiger bleken dan ze leken.
Begin hierParsware Platform
New to Parsware Platform? This is the reading list. Every article in the series, in the order that builds step by step, from your first table to processes, reports, portals and AI, with each one linked as it is published.
Lees het artikel
Begin hierFor Power Apps
The reading list for Parsware for Power Apps, the managed solution that adds pixel-perfect reports and drawn screens to Power Apps. Every planned article in order, linked as each one is published.
Lees het artikel
Parsware Platform
A component that looks different when pointed at, or in a state your screen decides, and an interface each copy is given: properties it shows and events it raises. Drawn, not coded, and nothing runs when the pointer moves.
Parsware Platform
Make a component from what you selected, place as many copies as you like, change the original and every copy follows, even in another app. Trying it, we fixed a component that left its words behind when you typed a new position, a menu that named the command differently from everywhere else, and text that started out in the wrong font.
Parsware Platform
One colour, text style or shape style used everywhere and changed in one place, and design tokens that make it follow light and dark mode. Trying them, we fixed three things in the style dropdown: it ignored the keyboard, showed every token as the same blue, and squeezed its own banner.
For Power Apps
A canvas app and a Parsware Studio screen are both screens you design yourself, and both can sit on a model-driven form. They behave very differently once they're there. Here is what each one is good at, and how to choose.
Parsware Platform
How a shape behaves when its frame changes size: pinned to an edge, stretched between two, kept in the middle, or scaled with the frame. Set once, it holds on the canvas and on every screen size the app runs on. Trying it, we found the ten choices were English in every language, and fixed that.
Parsware Platform
Rows and columns that arrange themselves: a frame that lines up what is in it with one gap and one padding, keeps it lined up as you add things, and lets one child take the spare room. Trying it, we fixed Ctrl+D, which used to drop the copy on top of the next item instead of into the row.
Parsware Platform
Solid colours, design tokens that follow light and dark mode, linear and radial gradients, and icons from the platform's library. Trying them, we found every icon drawn as a solid blob on the canvas, and fixed it.
Parsware Platform
Placing text, giving one word its own weight and colour, fonts and sizes, and choosing whether the box fits the words or the words fit the box. Trying it, we fixed two things: you can now type as soon as you place a text, and styling after typing reaches the whole line.
For Power Apps
Power BI paginated reports and Parsware reports both produce a document laid out to the page, and both can read Dataverse. They are built for different jobs. Here is where each one fits, what each costs to read, and when you would use both.
Parsware Platform
Keeping shapes together as a group, combining them into one shape, and using one shape to frame another. Trying each, we fixed three things: double-click now reaches a shape inside a group, and a combined shape stays in its frame with its rounded corners.
Parsware Platform
Guides that line a shape up with its neighbours as you drag, and buttons that align, match and space several shapes at once. Trying them, we stopped the guides catching shapes that aren't on screen.
For Power Apps
When a paid Parsware licence passes its date, nothing stops. Reports and screens keep working for your users, the designer keeps working for your makers, and makers see a notice that renewal is due. A trial is different, because a trial is meant to end. Here are both, pictured with expired keys.
Parsware Platform
Drawing a shape, selecting one or several, and moving, resizing, turning, copying and stacking them. Trying each, we fixed three things: a new shape is now selected, the arrow keys move it, and a typed angle turns it in place.
Parsware Platform
A frame is a screen, a page or a box that holds other things. Start one at a phone's size, draw inside it, and turn it into a tablet: what's inside follows the rules you give it.
Parsware Platform
Pan with the wheel, zoom with Ctrl, and press Shift+1 to see the whole drawing or Shift+2 to fill the window with what you selected. Trying them, we found the zoom keys missing and added them.
Parsware Platform
Studio screens and reports are drawn on one canvas, the Graphic Designer. Here's where everything is: the toolbar, the tool rail, the layers and components on the left, the inspector on the right. Touring it, we fixed two small things in its right-click menu.
For Power Apps
Parsware for Power Apps runs inside your Dataverse environment. Your records are read in the browser as the signed-in user, and your designs are stored in Dataverse. The licence check makes no call. One request can leave, near a paid licence's expiry, and it carries the licence and nothing else. Here is what we measured.
Parsware Platform
A process moves between environments the way everything else does: in its solution, with its table, its form, its app and its roles. Import publishes it, and uninstall takes it out again. Trying that with a run still waiting, we fixed what happens to the run: it's now stopped, and its history says why.
Parsware Platform
A run's page says where one request has got to. A process's Insights screen says what keeps happening: how many runs got through, how long work waits before anybody picks it up, where runs stall, and how decisions usually go. Trying it, we fixed two things: decisions are named by their button, and the people view names people.
Parsware Platform
Every run of a process has a page: the route it has taken so far, where it is now, who it's waiting on, and everything that has happened, in order. From there you can pause it, stop it, or hand a waiting task to somebody else. We followed one change request from start to finish.
For Power Apps
A new release of Parsware for Power Apps is the same managed solutions at a higher version, imported over the ones you have. Nothing is uninstalled, and your designs, your licence and your data stay where they are. Here is what to import, in which order, and how to check it landed.
Parsware Platform
Small requests go to a department head, bigger ones to the finance director, the biggest to a committee as well. The bands live in a table finance edits, not in the process, so moving one changes who decides the next request. The sample said it worked this way and didn't; now it does.
Parsware Platform
A process can start by itself when a record is created, changed or deleted, or from a button on the record's form and list. Either way the run knows which record it's about. Running the sample as two people found a status that never changed and people named by their email address; both are fixed.
Parsware Platform
A step can be due within a set time, and when it isn't done, the process can offer it to somebody else as well or decide it by itself. A timer makes the process wait. We ran a support ticket through all three, and fixed five things on the way, starting with the designer turning every timer into a plain task.
For Power Apps
A published Parsware design is an ordinary component of your own solution, so it moves from development to production the way everything else in Power Apps does. Export the solution as managed and import it. Production needs the Parsware runtime and nothing else. Here is a report taken from one environment to another, every step pictured.
Parsware Platform
A purchase order goes to Finance and Legal at the same moment, two people decide on their own, and the process waits for both before it gives one answer. We ran it with Finance signing off and Legal refusing, and watched the run wait at the join in between.
Parsware Platform
An employee asks for a week off, their manager decides, and a branch sends the request one way or the other. We ran it as both people and read the run afterwards. The sample shipped with roles that only opened the app and a manager's step that said read-only; both are fixed.
Parsware Platform
A change request goes to one person, who may correct it, then to a second, who reads a report of it and approves or rejects. We ran it as two different people, and the run's history says who decided each step. Writing this we found four things that only an administrator never notices, and fixed them.
For Power Apps
A Parsware report can be written in Persian or Arabic. Type the words and each text box turns right to left on its own; lay the page out from the right, and the preview prints it the way a Persian or Arabic reader expects. Here is a report turned into Persian in a few minutes, and what follows the reader's language on a screen.
Parsware Platform
Save keeps your work; Publish changes what runs. Each publish is a numbered version, a run keeps the version it started on, and the line under the title says whether what you see is live. Writing this we found Publish stopping after it saved unsaved edits, and fixed it.
Parsware Platform
A drawn process that nobody's software follows is a poster. In Parsware the drawing is what runs: you draw who does what on swimlanes, publish a version, and the engine starts it from a record, sends each step to the right person's task list, and keeps a history of every run. This is how the three parts fit together.
Parsware Platform
A process design is a plain JSON file you can export, edit and import, and the import checks it before anything reaches the canvas. Export a picture, PNG or SVG, for a document or a slide. Trying both, we fixed two things: the pictures now carry the lane names, and a refused file names the missing node.
For Power Apps
A top bar, a menu or a footer that appears on every screen should be drawn once. In the Parsware designer that is a component, a main drawing with copies placed on each screen, and changing the main one changes every copy. Here is how components work in a Power Apps design, using the Starter app that ships with the samples.
Parsware Platform
When a process step reaches a person, they read what it opens and then decide. A coform is what they decide on: a few fields and the buttons that end the step. We built one in the parallel sign-off sample, put it on a task, and routed each button its own way. The field types now read as words.
Parsware Platform
The process designer checks the drawing as you draw it, and the corner of the canvas says what is still missing: a step nothing reaches, a step that leads nowhere, a timer that never fires, a misspelt variable. Selecting a line takes you to the thing it is about. Nothing stops you saving, but Publish now waits for the list to be empty.
Parsware Platform
A process carries values from one step to the next: what the manager decided, how many days were asked for. Each is a variable, declared once on the process with a name and a type, given a first value in On start, and read and written by name. We added one to the Leave Approval sample and misspelt another on purpose.
For Power Apps
Wherever the Parsware designer needs something from your Dataverse environment, a table, a view, a saved query or a column, it offers a list read from that environment rather than a box to type in. Here is every one of those pickers, what each lists, and the few places you still type a name.
Parsware Platform
A user task has to land in somebody's list. It goes to whoever its Assigned to answers, or failing that whoever holds its lane's role in the run's unit, and a step can refuse the person who started the run. We went through each on the Leave Approval sample, and found the help page telling people to write something that doesn't work.
Parsware Platform
Every step in a process can run code at the moments that matter to it: when the run arrives, when the task is given to someone, when they finish it, when the run leaves. A user task also works out who gets it and which record they look at. We opened the manager's step in the Leave Approval sample and went through all six.
Parsware Platform
A branch doesn't decide anything by itself. Each connection leaving it carries a condition, one line of BS that is true or false, and the run takes the one that's true. We read the conditions on the Leave Approval sample, tried to break them three ways, and fixed two things on the way.
For Power Apps
Every Parsware report and screen is drawn in one designer, which runs as a page inside the Parsware Studio app. This is a tour of it, from the list you open a design from to the toolbar, the layers, the components, the canvas and the properties panel, and what changes between a report and a screen.
Parsware Platform
You drag from one step to another to connect them, the designer draws the corners, and View → Auto arrange tidies the whole diagram without moving work between lanes. Trying it for this article found four things to fix: two kinds of overlapping lines, a drag that drew nothing, and a hint that was always in English.
Parsware Platform
A purchase order needs Finance and Legal to sign off, and neither should wait for the other. A Fork sends it to both at once, and a Join waits until they have both answered. We opened the parallel sign-off sample, and fixed three things on the way: unreadable labels, stray resize handles, and a Join whose most useful setting had no control.
Parsware Platform
A task's Type puts a small badge on the step: user, service, script, manual, send, receive, business rule. Only one of them changes what a run does. We went through the list on the two-step approval sample, and say plainly what each type does and what it only describes.
For Power Apps
Power Apps replaces a broken code component with six words, "Error loading control", whatever went wrong. The Parsware Runtime control says what is wrong instead, in its own space on the form, and the form designer shows it before you save. Here is every message, and what to do about each one.
Parsware Platform
Four shapes carry most processes: a start, tasks, a branch where the process decides, and a finish. We opened the two-step approval sample and clicked each one to see what it asks for and where it can connect, and found the designer letting a connection leave a Finish without a word. It says so now.
Parsware Platform
A swimlane named Manager tells a reader who does the work. It tells the engine nothing until you give the lane a Role, picked from the environment's security roles. We set one on the leave-approval sample, added a lane, and followed a role from the designer to the people who hold it.
Parsware Platform
A business process in Parsware is drawn, not coded. Lanes for who does the work, shapes for the steps, arrows for the order. We opened the leave-approval sample and went round the designer: the palette, the outline, the canvas, the properties panel, and the problems panel that checks the process as you draw.
For Power Apps
Everything a drawn screen does is written in BS, in a code editor inside Parsware Studio. The editor knows your Dataverse environment, so it offers your tables, then their columns, as you type, and it underlines a mistake before you save. Here is how to use it.
Parsware Platform
A security role says what somebody may do with a table. A data policy says which records that reaches, and when a save is refused. We imported a sample with one of each kind, gave its role to two regional managers, and watched the same grant show each of them a different list and refuse one of them an approval.
Parsware Platform
The same solution in two environments should call two different payment services, a sandbox in one and the real thing in the other, without anybody editing a script. That's what an environment variable is for. We installed one solution in two environments, gave each its own value, and saved the same order in both.
Parsware Platform
A loop that never ends is a typo away, and on the server it would hold a save open forever. So every script runs on a budget. We wrote two broken plugin steps, a loop counting the wrong way and a function with no way out, and read what the platform says when it stops them.
For Power Apps
One line in a button's Pressed opens a different published design over the form, a report in Power Apps' own dialog or a Studio app in its side pane, with the record you're on passed along. Here is openDesign, and how it differs from navigate and showModal.
Parsware Platform
A plugin step that runs after the response has nobody to tell when it fails. So it tries five times, and then it waits on a list. We made one fail for a real reason, read the failure, fixed the setting it needed, and pressed Retry.
Parsware Platform
Not every server rule refuses. This one approves. A claim of 50 or less is marked approved as it's saved, by a plugin step that sets a value on the record before it's written. We saved a taxi fare and a hotel bill, watched only one come back approved, then watched the sample's own lock stop the approved one being edited up.
Parsware Platform
The answer to "is there enough stock?" isn't on the order line. It's on the product. We saved three order lines against a product with 10 in stock and watched a plugin step read the product, take the stock and log the movement, or refuse the line, then read the script that does it.
Parsware Platform
A plugin step is registered against a table, a write, a stage and an order, and the stage decides the most. We put a second step behind the order-stock sample's own, watched a refusal before the write undo the stock the first step had taken, then moved the same refusal after the write and watched the order line stay.
For Power Apps
A screen on a form doesn't have to fit everything in its section. It can open a card in a modal over the whole page, or slide one in from either side as a drawer, and close it again. Each card is drawn once, beside the screen, and opened by name.
Parsware Platform
A server validation rule is a plugin step that refuses a save and says why. We added one from scratch, "a claim over 10,000 needs a purchase order", then watched the editor catch a misspelt function and the form show the step's message when we saved a claim that broke it.
Parsware Platform
A claim over 1,000 needs an approval note. The form can show that as you type, but only a plugin step makes it true, because it runs on the server whatever saved the claim. We imported a spreadsheet of claims past the form and watched two rows refused with the step's message, then looked at how one script holds the limit for both sides.
For Power Apps
A drawn screen can load real Dataverse rows when it opens, count them, chart them and list them. Here, a panel on the Case form shows how many cases there are at each priority and the five newest ones, read live as the signed-in user.
Parsware Platform
A form rule runs in the browser and changes the form as you type. In the Expense Approval sample, typing "rejected" into Status shows a Rejection reason and makes it required, and approving the claim hides it again and locks the amount. Here is the form, the three rules behind it, and the one script they share.
Parsware Platform
Parsware has several places to put a rule. Form rules make a form respond as you type. Plugin steps decide what may be saved, however it's saved. Custom APIs answer other systems, scheduled jobs run on a clock, and processes carry work between people. This guide says which one to reach for, with a real example of each.
Parsware Platform
BS Lang runs in two places. A form rule runs in the browser, in TypeScript; a plugin step or a Custom API runs on the server, in C#. Those are two separate interpreters of one language, so we keep them the same with one shared set of test scripts that both must pass. This is a developer's look at how that works, and at the two cases where they still disagree.
Parsware Platform
A server-side script can write a file to storage and read it back, and it can put a file into one record's File field. They're two different places for two different kinds of file. We exported expense claims as a CSV into a bucket, then attached a receipt to one claim and found it on the claim's form.
For Power Apps
A drawn field can work with more than the column it sits on. Bind up to three more columns to the same Parsware Runtime component, and the screen reads them all and writes any of them by name. Here, choosing a contact channel also fills in the case's next step.
Parsware Platform
sendEmail sends a message through a mail service the environment names, just like callService. It never stops the script. It tells you whether the email went, and the script decides what to do about it. In the sample, a paid order records Sent or Not sent with the reason. Here is the call, what the mail service receives, and why an email step shouldn't refuse a save.
Parsware Platform
callService lets a server-side script post to another system, like a payment provider. The script never holds the address, only a service name. Each environment sets where that name points, so Test can use a sandbox and Production the real thing, and an environment that sets nothing reaches nothing. We took payments in a sample order app, and saw an answer, a refusal and a missing setting.
Parsware Platform
When a plugin step and a Custom API need the same rule, write it once as a solution script and import it into both. We used the Shared Server Logic sample, where an approval limit decides both whether an order saves and what an API tells a partner, then changed the limit in one line and watched both follow. Here is how import and export work, and which scripts can import.
For Power Apps
Some values are easier to pick than to type. A drawn field is a Studio screen placed on one column of a model-driven form. It shows the column's value and writes it, and the form saves it like any other change. Here's a contact-channel field with three buttons in place of a text box.
Parsware Platform
A server-side script can read more than the record it's working on. getRecord fetches one record, queryRecords and countRecords match one field, and runQuery takes a whole query with and/or filters, joins and totals. We used them in a plugin step that refuses an invoice when a customer would go over their credit limit, and in a Custom API that joins two tables.
Parsware Platform
Every Parsware script is BS Lang, but a form rule, a plugin step, a Custom API and a step in a process can't call the same functions. What each one gets depends on where it runs and what it has in front of it, a form, a record being saved, a caller or a running process. Here is each list, why it differs, and what happens when you call a function from the wrong one.
Parsware Platform
Completion helps once you know roughly what to type. The eye button answers the question before that, what can this script call at all, with every function the script can use, its arguments and a line on what it does, in a list you can search. Here is where it is, what it lists, and the one-line version on a Studio binding that inserts what you pick.
For Power Apps
A model-driven form is a column of fields. Sometimes a record needs something else beside them, such as guidance, a checklist, or a panel with its own buttons. With Parsware you draw that part as a Studio screen and put it on the form, where it sits with the record's fields and moves between screens without the form reloading.
Parsware Platform
Open a bracket after a function name and the BS editor shows what the call takes, with the argument you're on in bold and, for a function with several forms, each one to page through. Shift+Alt+F tidies the whole script, keeping your comments and your line breaks. Here is what each one does, and when formatting leaves a script alone.
Parsware Platform
The BS editor offers names as you type. At the start of a line it lists the functions the script's host provides, the functions it imported from a solution script, and its own variables. After a dot it lists the value's methods. Here it is in a form rule from the Expense Limit sample, with what it offers and what it leaves to you.
Parsware Platform
The BS editor checks a script while you write it. A mistake is underlined within half a second, hovering says what is wrong, and a problems list under the script counts every error, jumps to each one and copies them all as text. Here is what it catches, and what it can't.
For Power Apps
The fastest way to a report of your own is often one that already works. The Parsware samples come with an editable copy of each drawn design, so you can rename one, change it and publish it into your own solution, while the original stays exactly as it shipped.
Parsware Platform
BS Lang is the one scripting language in Parsware, used by form rules, buttons, plugin steps, Custom APIs, processes and Studio screens. If you know a little JavaScript you can read it already. Here are variables, lists, objects, functions, conditions and loops in one short script, and the few places it differs.
Parsware Platform
A Parsware query can answer "how many" and "how much" as well as "which". Group records by a column, count and sum them, keep only the groups that pass a test, and take the top five, all in the query designer, with the database doing the arithmetic.
Parsware Platform
A saved query in Parsware is one question with one definition. A report fills its table from it, and a server script runs it by name, so correcting the question once corrects every answer that names it, in this environment and in the next one the solution goes to.
For Power Apps
A query pasted into a report lives in that one report. A saved query lives once, has a name, and can be published into a solution beside the reports that use it, so it arrives in Test and Production with them. Here's the expense totals query from earlier, published and named by a report.
Parsware Platform
A saved query in Parsware is a question your solution owns. Build one in the query designer from a table, the tables joined to it, the columns it returns and the conditions that narrow it, and every save is checked against the environment's real tables before anything can use it.
Parsware Platform
The charts on a Parsware dashboard do more than sit there. Hover over a bar or a slice for its exact number, and select a legend entry to hide that series, so the rest can be read on its own. Here is what each one tells you, and the one thing to watch for.
Parsware Platform
When a Parsware business process needs a person, it sends them a task. My tasks lists yours; opening one takes it and shows what it is about, and Decide finishes it with an outcome such as Approve or Reject, after which the process moves on by itself.
For Power Apps
In Parsware for Power Apps, Save keeps your work and Publish releases it. Readers only ever see what was published, so you can work on a live report without anyone watching it change. Here's a change to the case sheet, saved, checked on the form, then published.
Parsware Platform
Every Parsware record has an owner, a person or a team, and the owner decides who can see it once access rules are set up. Hand a record on from its Owner field on the form, pick User or Team, and save.
Parsware Platform
In Parsware every environment has its own web address, so moving from Development to Test is opening Test's address, not choosing from a menu. Bookmark each one, and two browser tabs can never be confused about which environment they are in.
Parsware Platform
Most of a working day in a Parsware app is spent in a view, the list of one table's records. Sort by one column or several, search, build a filter with And and Or, select records, open one, save it, and delete what you no longer need.
For Power Apps
A report laid out to the pixel has to survive the printer. Parsware reports print one report page per sheet, with nothing split across two, no blank sheet at the end, and no browser furniture in the margins. Here's where Print is, what it does in each place a report appears, and what comes out.
Parsware Platform
Deleting a table in Parsware removes its definition and its data from the environment, so the platform first checks what still depends on it. A lookup that points at the table, or an app that shows it, blocks the delete and is listed by name.
Parsware Platform
Every Parsware environment comes with an Organisation app. It holds your units as a chart, the people in each one, and who does which kind of work where, which is what processes route work by and what "my unit and below" access is measured against.
Parsware Platform
In Parsware, saving a table is applying it. The database table and its columns exist before the screen comes back, a form and a view come with it, and a change that would cut stored data short is refused.
For Power Apps
One Parsware component on a form can show a different report for each record. It reads the report's name from a column, and falls back to a default when the column is empty. Here the Case form shows an urgent-case notice for one case and the ordinary case sheet for the rest.
Parsware Platform
Every table keeps four stamps for you, Created On, Created By, Modified On and Modified By, plus an Owner. Put them in a view or on a form and people see names and dates, not ids, with nothing to set up.
Parsware Platform
A dashboard in Parsware is a screen you draw. Counted tiles, charts, the table's own grid and its quick create form sit on one page, and the page goes into an app's navigation like any table.
Parsware Platform
A command bar can use your organisation's words and follow the order people work in. Rename the platform's own commands, hide the ones a list doesn't need, drag everything into place, and divide it into groups.
For Power Apps
A Parsware report can sit on a model-driven form, beside the record's own fields, and show only that record. One setting on the report's dataset does the narrowing, and one component on the form does the showing. Here's a case sheet on the Case form.
Parsware Platform
Add your own buttons to a list's or a form's command bar. Most need no code, because they open a view, start a record or open an address. When the button depends on what the user ticked or typed, it runs a short script.
Parsware Platform
Any table with a date can be read as a calendar. Pick which field says when a record starts, colour the blocks by a choice, and people click an empty slot to book it, with the rooms side by side on the day sheet.
Parsware Platform
A timeline puts every call, email, meeting and note about a customer in one column on their form, newest first. Filter it by kind, start a new one already filled in, and set it up in the Form Designer from any table that points at the record.
For Power Apps
Dataverse stores a lookup as an id and a choice as a number, and neither belongs on a printed page. A Parsware report prints the related record's name and the choice's label instead, with no extra work. Here's a list of cases with the contact each one belongs to and its priority.
Parsware Platform
Two small views decide how people pick a record in a lookup. A lookup view chooses the columns of the Advanced lookup grid, and a quick find view chooses which columns typing searches, so "Berlin" finds the contacts in Berlin.
Parsware Platform
Build a filter from conditions in groups, each group either And or Or, and put one group inside another. Use it once while you browse a list, or save it on a view so everyone who opens the view gets it.
Parsware Platform
Each column of a view can have its own header, date format, alignment and control, without changing the field. Turn "Purchase Date" into "Bought", write dates out in full, line up the amounts, and show a yes-or-no column as switches.
Parsware Platform
A view is a list of a table's records, and it's where most people spend their day. Choose its columns, put them in order, give a column a width, and decide which list an app opens on.
For Power Apps
A view returns rows and can't add them up. For totals, counts and averages by group, a Parsware report reads a FetchXML aggregate, so Dataverse does the arithmetic and the report prints the answer. Here's a table of expense totals by currency and status, from one pasted query.
Parsware Platform
A field's type decides what it stores. Its control decides how people fill it in. Turn a yes-or-no field into a switch with its own words, show a date in the Persian calendar, and put a control you built yourself on a form.
Parsware Platform
A note is fixed text on a form, like a heading, an instruction or a warning, written in Markdown and shown beside the fields it's about. Here is how to add one, what it can contain, and why it can't be used to slip markup into a form.
Parsware Platform
A form is tabs, rows and sections, with a header that stays put whichever tab is open. Lay one out in the Form Designer, give a table a second form for a different team, and let people switch between them on the record.
For Power Apps
A Parsware report can read a Dataverse view instead of the whole table. The view decides which rows, in what order and with which columns, and it's something your makers already know how to build. Here's a report of urgent cases, filtered and sorted by a view.
Parsware Platform
Building an app doesn't give it to anyone. Share it with a role, check who that actually reaches, and the app appears on their launcher and nobody else's. The sharing travels in the solution, so you don't redo it in every environment.
Parsware Platform
When two people edit the same record and both press Save, the second save is refused instead of silently overwriting the first. Here is what each of them sees, and how to carry on.
For Power Apps
A Parsware report is a page you draw and bind to a Dataverse table. This walks through the whole loop once in Parsware Studio. Create the design, name the table it reads, point a repeating row at it and bind two columns, and you end with 200 real rows on eight printed pages.
Parsware Platform
Turn auditing on for a table and every create, update and delete of its records is recorded, with who made the change and what each field was before and after. Leave out the fields that don't matter, and read a record's history in the Audit Log.
Parsware Platform
Load a CSV file into a table. See what is in each column before you import, map columns to fields, and get the rows that failed back as a file to fix, with a reason on each one.
Parsware Platform
A table whose records have a parent of their own kind can be shown as a tree, with another table's records hanging underneath, the selected record's form beside it, and a check that stops a branch being moved inside itself.
Parsware Platform
Choose one field as a table's record image and one as its secondary text, and every list and lookup shows a picture and a second line beside each record's name. Two contacts with the same name stop looking the same.
For Power Apps
The Parsware Samples solution brings two small tables, eight finished reports, two Studio apps and an app that opens them. The tables arrive empty, because a solution carries components and not rows, so one page fills them with 200 rows each. Here is what's in it and how to fill it.
Parsware Platform
A file too big for the environment's database is moved to object storage on its own. The form, Download and who may read it all stay the same, and deleting the record deletes the file.
Parsware Platform
A File field holds a document and an Image field holds a picture, each belonging to one record. Add one to a table, attach a file on the form, and see what Save, the size cap and the record's permissions do with it.
Parsware Platform
A table's constraints are rules the database itself enforces: no two records may share a code, and no two bookings of one thing may overlap. They hold for a form, an import, a script and two people saving at the same moment. We imported the Court Bookings sample and tried to break both.
For Power Apps
Parsware for Power Apps installs two model-driven apps. Parsware Studio is where makers draw reports and screens, and it only exists in development. Parsware is what every environment gets, and it starts almost empty on purpose, because the reports and screens your users open belong in your own apps.
Parsware Platform
An auto-number field gives every new record a reference like EQ-2026-00001 the moment it is saved. Nobody types it, nobody can change it, and nobody has to look up the last one used. We imported the Enquiries sample, saved a few enquiries, and changed the format halfway through.
Parsware Platform
Every table has a State and a Reason. Design the lifecycle your records move through, with a reason under each state, colours and icons that read at a glance, and numbers from your publisher's range.
Parsware Platform
An option set is a list of choices you define once and use on any table. Each option can have a colour and an icon, and gets a number from your publisher's range that never changes, so renaming is safe and two publishers' lists never collide.
For Power Apps
A Parsware for Power Apps licence is one line of text, signed for your tenant and the environments it covers. You paste it into a form in the Parsware app, and the form tells you what the key covers before you save it. Nothing is sent to us to check it.
Parsware Platform
Every relationship in Parsware is one-to-many, made by a lookup, and read as many-to-one from the other end. Here is how to see both directions, how to model many-to-many, and why a record that others still point at can't be deleted.
Parsware Platform
Sometimes a link can point at more than one kind of record. A course is booked by a company or by a person. In Parsware that's one field, a lookup to several tables, with a tab for each table on the form and a Related tab on both.
Parsware Platform
A lookup field links a record to one in another table. Adding one also creates the relationship between the two tables, gives the form a search that finds records as you type, and puts a Related tab on the record at the other end.
For Power Apps
Parsware for Power Apps arrives as three managed solutions. The runtime goes into every environment and goes in first, the designer only into development, and the samples wherever you want to try things. This is the whole install, in the maker portal or with the Power Platform CLI.
Parsware Platform
Make a field required once and every form asks for it. Make it read-only on one form and it's shown but not edited there. Give it a default control and format, and every form and view shows it the same way.
Parsware Platform
Text, numbers, yes/no, dates, option sets, lookups to one table or several, files and images. What each field type stores, the settings it takes, and the control a form shows for it, built on one table.
Parsware Platform
A tour of the maker portal, where Parsware applications are built and run from. Home, the rail, the environment picker, help, languages, appearance, and the list and drawer controls every screen shares.
For Power Apps
Parsware for Power Apps is a managed Dataverse solution that adds two things to model-driven apps. Reports laid out to the pixel and bound to your tables, and screens you draw and place on a form. It runs entirely inside your tenant, and your data never leaves it.
Parsware Platform
A step-by-step walkthrough, from an empty solution to a working app. Create a table, add five kinds of field, build a filtered view, and open it with real rows in about ten minutes.
Parsware Platform
How Parsware names your work, packages it and moves it between environments. Create a publisher and its prefix, build a solution in development, export it, import it into test as a managed solution, and uninstall it cleanly.
Parsware Platform
What Parsware is and how its parts fit together, shown through one real application, from the tables underneath it to the phone screen, the approval process and the printed report.
