15 مقاله نوشتهشده در ۱۴۰۴ بهمن.
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.
