Export Operation
The Export Operation captures the current state of your data quality artifacts and writes them to your linked enrichment destination as queryable outputs. You can export anomalies, quality checks, and field profiles. Once exported, the data is available alongside the rest of your workspace data for downstream analysis, BI, governance reporting, and audit trails.
Enrichment destination required
An enrichment destination must be linked to the source datastore before you can run an Export Operation. The exported outputs are written there.
Show me how
The app can walk you through this. Click Show me how in the Export dialog's header, or press H while it is open, and the Run an Export walkthrough highlights each step while you fill in the real form. See The How-tos Scope for every way to start one.
Deep Dive
-
Introduction
A high-level overview of what the Export Operation captures and why it matters.
-
How It Works
Mechanics: asset types, container selection, async behavior, size limits, the
_<datastore>_export_<asset>output-name pattern, and re-run semantics. -
Field Masking
How field masking applies to Field Profile exports and how to reveal masked values.
-
Export Schema
Fields recorded in each exported output for anomalies, quality checks, and field profiles.
-
Permissions
Who can trigger, schedule, and re-run Export Operations.
How-tos
-
Run Export
Step-by-step walkthrough of the Export Operation modal.
-
Schedule Export
Configure Hourly / Daily / Weekly / Monthly / Cron schedules in any IANA timezone.
-
Review Exported Data
Open the exported outputs from your enrichment destination.