Configure an Export Action¶
Add an Export action to export data quality metadata (anomalies, quality checks, or field profiles) to the enrichment destination automatically whenever the Flow's trigger activates.
Permission Required
To edit and publish a Flow, you need the Editor team permission on every datastore it relates to. Admins are exempt. See Flow Permissions for details.
Initialized datastores connected to an enrichment destination only
The Datastore dropdown only lists source datastores that are initialized and have an enrichment destination connected. A source datastore becomes initialized after successful Sync, Profile, and Scan runs. An enrichment datastore becomes initialized after Sync and Profile.
Field reference¶
The Export Settings panel shows the following fields. They mirror the options of running the operation directly on the datastore.
Select the datastore first
The sections below live in the Operation Configuration stepper and stay disabled until a Datastore is selected. For DFS datastores, the Select step lists File Patterns instead of Tables.
| Field | Required | Type | Description |
|---|---|---|---|
| Datastore | Option | The source datastore to export metadata from. |
Select Tables¶
Choose which tables the export covers. Picking one of the options is required to move to the next step, and All is preselected.
A datastore with no tables
When the datastore has no tables, a warning above the options reads No tables were found in this datastore. Run a Sync, or check the connection settings and permissions. (on a DFS datastore it starts with No file patterns were found). Run a Sync operation on the datastore first, or fix the connection settings or the database user's permissions so the Sync can see the tables.
Choose Metadata¶
Choose the metadata to be exported. Picking one of the options is required.
Options¶
The Options change with the chosen metadata.
| Field | Required | Type | Description |
|---|---|---|---|
| Include Archived | Checkbox | Includes archived anomalies or quality checks in the export. Only shown for Anomalies and Quality Checks. | |
| Merge with Source Records | Checkbox | Writes each anomaly beside the source records it flagged, to a separate output instead of the regular Anomalies output. Only shown for Anomalies. See Merge with Source Records. | |
| Reveal Masked Values | Checkbox | Exports masked field values as plain text. Only shown for Field Profiles. |
Steps¶
Step 1: Navigate to the Flows page by clicking Flows on the left side panel.
Step 2: On the Definitions tab, click the Flow. On its canvas, click the dashed Action placeholder after the trigger, or the + handle at the bottom edge of a node.
Step 3: In the List of Actions panel, pick the Operation category, then click Export. The Export Settings panel opens on the right-hand side.
Step 4: Fill in the fields.
Step 5: Click Save. The node shows a CHANGED badge and the You have unpublished changes banner appears on the canvas.
Step 6: Click Publish to make the action live.
Info
Export nodes display the asset type in their titles (e.g., "Export Anomalies") to help you identify the exported content easily.