Export Operation
The Export Operation captures the current state of your data quality artifacts and writes them to your linked enrichment datastore as queryable tables. 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 datastore required
An enrichment datastore must be linked to the source datastore before you can run an Export Operation. The exported tables land in that enrichment datastore.
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, the
_<datastore>_export_<asset>table-name pattern, and re-run semantics. -
Field Masking
How field masking applies to Field Profile exports and how to reveal masked values.
-
Export Schema
Columns recorded in each exported table 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 tables from your enrichment datastore.