12 articles about Reports, in reading order.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
Reports
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.
