Exports

Reporting exports to PDF, CSV and XLSX. Which of those you get depends on what you are exporting, and the rule is simple enough to state in one line:

A preset exports to PDF. A table exports to PDF, CSV or XLSX. A report exports to PDF.

A preset is a composed page — KPI tiles, donuts, trends, rosters, laid out deliberately. Flattening that into a spreadsheet does not produce “the same data in another format”; it produces a pile of unrelated result sets with the arrangement thrown away, which is precisely what made the preset worth having.

A table is the opposite: one tidy result, which is exactly the thing a spreadsheet is for. So tables get all three formats.

If you want a preset’s numbers in a spreadsheet, find the table template covering the same ground — most areas have both. The catalogue marks the kind of every template.

Export on a dataset row opens the dialog.

Format, period and row limit — the three things a single export may override.

Format offers only what the dataset’s kind supports.

Period defaults to the dataset’s saved period, so an export matches what you saw on screen. Choosing custom date range overrides it with fixed dates for this one export — it does not change the dataset. Leaving the range empty exports all time, which is now an explicit choice rather than a silent default.

Row limit defaults to the dataset’s limit. Leave it blank to export every row up to the server’s ceiling.

If an export hits the row limit, you are told: the notification names how many rows were written and says the limit was reached, and the file is flagged as truncated rather than quietly ending early.

That matters for evidence. A CSV that stops at ten thousand rows with no indication looks exactly like a CSV of ten thousand rows, and the difference can be the whole finding. If you see the truncation notice, narrow the period or raise the limit and export again.

Download PDF, from the report list or from the builder. The report must be saved first.

The exported PDF is byte-for-byte what the preview showed. Both are produced by the same server-side render — the preview is not a browser approximation of the document, it is the document. There is no class of problem where it looked right on screen and came out wrong in the file.

Exports are delivered as file downloads with the dataset or report name in the filename, encoded so that names in Cyrillic and other non-Latin scripts survive the trip intact rather than arriving as a row of question marks.

Exporting needs reports:export. It is separate from reports:view and reports:run on purpose: you can let someone read reporting on screen without letting them carry the data out of the product. Someone without it sees the export controls disabled with an explanation rather than a silent failure.

• Datasets — where the saved period comes from
• Reports — composing the document a PDF is made of
• Scheduled delivery — the same files, mailed automatically