Reports
Read every number and column on Reports and preserve the evidence scope behind exported files.
What you see on Reports
Reports is the project file history for saved exports. The three cards show all report export records, CSV records, and PDF records for the project. CSV Reports equals records whose stored format is CSV; PDF Reports uses the same rule for PDF. The total can include another supported format if one is added, so do not assume it must always equal CSV plus PDF.
Report History displays the 25 most recent records. The cards count the full project history, while the table is deliberately limited; a larger card count than visible rows is expected and does not mean files are missing.
File metadata and status
| Column | Meaning | ||
|---|---|---|---|
| Filename | Generated storage name for the export. | ||
| Report type | The source report or section | converted to a readable label. | |
| Format | Stored export format such as CSV or PDF. | ||
| Status | Whether file generation completed | is pending | or failed. |
| Generated at | Stored generation timestamp shown as a date or a dash when unavailable. | ||
| Size | Stored byte size converted to a readable unit; it is not row or answer count. | ||
| Generated by | Member name | or System when no user is attached. |
How reports enter the history
Exporting Overview or a supported detail section creates a project report record. A generated record receives a Download link. Pending or failed records do not present a valid generated file as evidence. Creating another export produces another historical record rather than changing the data inside an older file.
A report captures the applicable project and filter parameters at generation time. It does not automatically refresh when later runs complete, aliases change, products are rescanned, or filters are edited in the browser.