31 articles about Reports, in reading order.
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.
Parsware Platform
Why reports in Parsware are drawn rather than generated: a page laid out on a canvas, filled by a saved query when somebody presses Print, paginated, printed one to one on the paper it was designed for, and still text you can select and search.
Parsware Platform
A new report over the expense table: a dataset that names a saved query, a starter page from the Insert menu, a repeater over the claims, three columns bound to fields from a picker, and a preview with the real rows, two pages of them.
Parsware Platform
One report with three page designs: a cover with no header, the claims with a page header, column headings and a footer, and the terms on their own sheet. What each band is, how a section differs from a page break, and how the column headings come back on every sheet the table reaches.
Parsware Platform
Three totals on one report and a table of groups: a total row under the claims, a per-page total in the footer, and the claims by status from a saved query that groups, with a total of its own. Where each total looks, and why grouping belongs to the dataset.
Parsware Platform
Zebra rows from the row number, large amounts in red and bold, a status that disappears once the claim is paid, and each group's share of the whole as a percentage. Every one is a short expression on the report designer's Code page, and every format is one picker.
Parsware Platform
A bar chart of the claimed total by status, added to Claims by status: Insert → Bar chart puts a chart frame on the page, two expressions on the Code page give it values and labels, and the engine draws it, the same in the preview and on the printed sheet.
Parsware Platform
A report can print a real, scannable Code 128 barcode or QR code, either with a fixed value or one per row from the data. The Report Barcodes sample shows both, and a QR code in the page header of Claims by status takes whoever scans the printed sheet straight to the live list of claims.
Parsware Platform
A report's page frame is its sheet of paper: 595 by 842 is A4. Turning Claims by status landscape is a matter of telling the bands to follow the paper, then swapping the width and the height. The margin decides how much of each sheet the rows get, and Print / PDF prints exactly that sheet, with nothing the browser adds.
Parsware Platform
A printed invoice is one record and its lines. Two datasets with record fields say so: the invoice by its id, and the lines by their lookup to it. The designer's Invoice sample supplies the layout, and each of its texts is pointed at the real columns on the Code page.
Parsware Platform
A report is reached on purpose: from an app's navigation, where it opens over the whole table, or from a command drawn on a form, where it prints the record that is open. Claims by status goes on the rail of a Billing app, and a Print invoice button on the invoice form prints that invoice and only its lines.
Parsware Platform
A report prints what its saved query returns, so the query is where the work goes. A query that joins each invoice to its customer gives the Money owed report the customer's name and credit limit, and widening the query to overdue invoices changes the report without touching it.
Parsware Platform
A report in Persian has two parts. Its words read right to left because of how the page is drawn. Its digits and dates are Persian because of who reads it: the same report prints 4,200.00 and 2026/09/29 for one reader and ۴٬۲۰۰٫۰۰ and ۷ مهر ۱۴۰۵ for another.
Parsware Platform
A reporting tool outside Parsware wants your data: which tables it may read, what their columns are, pages of rows, and totals. The reporting endpoints answer exactly that, read-only, and only what the application's role may read. We pointed the front-desk dashboard at them, and ran a saved query by name.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
For Power Apps
Describe a report in a sentence and the Parsware designer draws it, bound to your own Dataverse table. It runs on an AI Builder prompt in your tenant, with no key and no outside service. Here is a case list with a page count, column headings and a total, generated in about twenty seconds, then corrected by hand.
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.
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.
