Export validation results

Goal

You'll download the validation-results list as a CSV or an Excel workbook (.xlsx) for sharing outside PLACEHOLDER Cloud — pulling a slice into a BI tool, attaching it to an audit ticket, or handing a stakeholder a snapshot without giving them an account. The export honours whatever filters you've set on the Results page, so the file matches exactly what's on screen.

CSV and Excel (.xlsx) export are shipped. PDF export is the browser's own "Print / Save as PDF" dialog — there's no separate server-rendered PDF (see the print section below).

Prereqs

• Workspace viewer role or higher. The export is gated by the same can_view_results permission as the Results list — if you can see the results, you can export them. A billing-only seat cannot.
• At least one ValidationResult in the workspace (run a checkpoint first).

Steps

Export the filtered Results list as CSV or Excel

1. Open the Results page. Navigate to Results in the sidebar.

2. Apply any filters you want in the export. The filter bar narrows the list by rule group, pass/fail status, and a run_time date range. The export carries these same filters, so a filtered table produces a filtered file.

3. Click "Export" and pick a format. The Export button is in the top-right of the page header. Choose CSV (.csv) or Excel (.xlsx). PLACEHOLDER Cloud streams the matching rows as an attachment and your browser downloads it as validation-results-<timestamp>.csv or validation-results-<timestamp>.xlsx.

Both formats carry the same columns and the same rows — only the container differs. Choose Excel when handing the file to a business stakeholder who lives in spreadsheets; choose CSV for a BI tool or warehouse load that wants raw text.

The download is an authenticated request (your session token is attached), so the link isn't shareable on its own — anyone you hand the file to gets the data, not a live endpoint.

Bulk export a date range for ETL

To pull a wider slice for a BI tool or a warehouse load:

1. Set the From / To date inputs in the filter bar to the window you want (e.g. the last calendar month).
2. Leave the rule-group and status filters on All if you want every run in the window.
3. Export → CSV (or Excel).

The export is capped at 50,000 rows per request (the same cap for both formats). If your range exceeds it the request returns a 400 asking you to narrow the date range — split a large backfill into a few smaller windows.

Columns

Both the CSV and the Excel workbook have one row per ValidationResult, with these columns:

Column	Meaning
run_time	When the validation ran (ISO-8601).
checkpoint	The configured checkpoint name (blank if the run had no checkpoint).
data_asset	The data asset the run validated, when recorded on the result.
rule_suite	The rule suite name (blank if none).
status	pass or fail, derived from the authoritative success flag.
success	true / false — the raw success flag.
severity	The recorded severity when present, otherwise ok (pass) / error (fail).
batch_kind	The partition kind for per-partition runs (column_partition, interval), blank for whole-asset runs.
partition_value	The partition value the run validated.
result_id	The result's UUID — use it to deep-link back to the detail page.

The CSV opens with a #-comment preamble carrying the organization id, workspace id, the export timestamp, and the active filter criteria, so a file that's been passed around still says when it was taken and what it was scoped to. Most spreadsheet and BI importers skip # comment lines; if yours doesn't, delete the leading # lines before the header row.

The Excel workbook carries the same metadata as a small labelled block (organization id, workspace id, exported-at, filters) above the table, with the header row frozen so it stays visible while you scroll a large export.

Use the API directly

The same endpoint backs both formats — add format=xlsx to switch from the default CSV:

GET /api/v1/organizations/{org_id}/workspaces/{workspace_id}/validation-results/export?format=xlsx&status=fail

Omit format (or pass format=csv) for the CSV. All the list filters (rule_group_id, checkpoint_id, status, start_date, end_date, …) apply to both.

Save a printable PDF

PDF export is the browser's own print dialog — there's no separate server-rendered PDF endpoint.

1. On the Results page, click Print / Save as PDF.
2. In the browser print dialog, choose Save as PDF as the destination.

The page carries a print stylesheet, so the PDF is content-only — the left navigation, the top search bar, the footer, and the build stamp are dropped, and the printed report flows across pages instead of being clipped to one screenful. The filters you've set still apply, so the PDF matches the on-screen, filtered (and drill-down-scoped) view. For a tabular extract you want the CSV or Excel export; the print-to-PDF path is for a quick visual snapshot to drop into a deck or email.

Verify

• Clicking Export → CSV downloads a validation-results-*.csv; Export → Excel downloads a validation-results-*.xlsx.
• Opening the CSV shows the # preamble, then the header row, then one row per result that was visible under your current filters. The Excel workbook shows the labelled metadata block, then the (frozen) header row, then the same rows.
• Setting a status filter to Fail and re-exporting yields a file containing only failing runs — both formats track the on-screen list.