Stamping Reports
Stamp Report creates a durable Report from a live saved Report Blueprint: it stores a Report PDF and downloads it. Preview Report uses the same print pipeline but downloads a PDF without creating a Report.
Reports are PDF-first. There is no hydrated interactive viewer, Drilldown Data retention, or Hydrated Reports capacity limit.
Stamp Report vs Preview Report vs Download
Section titled “Stamp Report vs Preview Report vs Download”| Action | Creates a Report? | Stores Report PDF? | Collects Report Generation Parameters? |
|---|---|---|---|
| Stamp Report | Yes | Yes | Yes, when the blueprint declares any |
| Preview Report | No | No | Yes, when the blueprint declares any |
| Report Download | No (existing row) | Already stored | No |
Use Stamp when you want history. Use Preview to check the PDF. Use Download from Report History to fetch a file you already stamped.
How to Stamp From the Editor
Section titled “How to Stamp From the Editor”- Open a Report Blueprint from Reports
- Save your composition (Stamp / Preview also dirty-save when needed)
- Click Stamp Report in the editor header
- If the blueprint declares Report Generation Parameters, enter values in the modal
- Wait for the print job; the Report PDF downloads when ready
- Find the new row later under Report History (
/reports/history)
Preview Report follows the same steps but does not add a history row.
Both actions require Report Write Permission and share a busy gate with Save and Reload Data.
What Gets Captured
Section titled “What Gets Captured”When Stamp succeeds:
- The print pipeline renders the blueprint’s sections and typed Report Elements
- A Report stores metadata plus a pointer to the Report PDF in object storage
- The PDF is the deliverable and the data snapshot for that run
Editing the blueprint afterward does not change Reports already stamped. Deleting the blueprint does not delete its Reports or Report PDFs.
Report Generation Parameters
Section titled “Report Generation Parameters”If the blueprint declares parameters:
- Stamp and Preview collect them through the same string-field modal
- Element queries and text interpolation can consume those values
- History Report Download never re-prompts; it returns the stored PDF as stamped
If no parameters are declared, the modal is skipped.
Finding Stamped Reports
Section titled “Finding Stamped Reports”Open Report History from the blueprint list header, or go to /reports/history. Soft redirects from older paths such as /reports/generated and /reports/report also land on history.
From history you can download, email, or delete Reports. See Report History.
Use Cases
Section titled “Use Cases”Month-end client packs: Stamp a Report at period close and email the Report PDF.
Parameterized deliveries: Declare an id parameter and Stamp once per recipient value.
Layout checks: Preview Report before stamping so history stays clean.
Limitations
Section titled “Limitations”- Stamp / Preview require write permission; download from history can be available with list access
- There is no Company-scoped report-count or Hydrated Reports Tier Limit for Reports
- Reports do not refresh on open; Stamp again for newer data
- Preview does not create a Report row—Stamp if you need history or email from a stored PDF
Troubleshooting
Section titled “Troubleshooting”Stamp or Preview fails or times out:
Large blueprints or heavy charts/tables can take longer. Retry once; if it keeps failing, simplify the blueprint or contact support.
Parameter modal appears unexpectedly:
The blueprint still declares Report Generation Parameters. Clear unused declarations from the blueprint definition if they are no longer needed.
History is empty after Preview:
Preview never creates a Report. Use Stamp Report to persist and download.