Link an Enrichment Destination
Linking a datastore to an enrichment destination gives Qualytics a place to write its findings: scan results, source record examples, remediation snapshots, materialized copies, and exports. The destination is another datastore; pick one that exists, or create it from inside the same dialog.
Permission Required
You need at least the Member role and the Editor team permission on the datastore to link a destination or change the settings. Creating a destination from inside the dialog needs the Manager role. See the Permissions page for details.
Link During Datastore Creation
You can also link the destination while creating the datastore, in the second step of the Add Datastore page. See Link Enrichment on Datastore Creation.
Field reference
The Enrichment Destination dialog is organized in these sections:
Prefix
| Field | Required | Type | Description |
|---|---|---|---|
| Prefix | Text | The start of Scan, Remediation, and Materialize output names. Export output names use the datastore name instead. Each datastore sharing a destination needs its own prefix; Qualytics refuses a prefix another datastore already uses on the same destination. |
Datastore
| Field | Required | Type | Description |
|---|---|---|---|
| Use existing | Option | Pick an existing enrichment datastore as the destination. Selecting one shows a read-only Details block with its Teams, Host, Database, and Schema (the URI and Root Path for file-based connectors). | |
| Add new | Option | Create an enrichment datastore here and use it as the destination: choose a connector, fill in its connection fields or reuse a saved connection, and give the new datastore a Name and its Teams. Only connectors Qualytics can write to are listed; see Supported Connectors and the connector's own page for its fields. Offered to users with the Manager role. |
After each write
| Field | Required | Type | Description |
|---|---|---|---|
| Sync and profile the enrichment destination | Toggle | On by default. After this datastore writes to the destination, Qualytics syncs the destination and profiles the new containers, so they are ready to use without a manual step. Turn it off to sync the destination yourself. |
Remediation Strategy
| Field | Required | Type | Description |
|---|---|---|---|
| Remediation Strategy | Choice | Whether a Scan also writes a snapshot of the anomalous records: None does not (default), Append adds the anomalous records after each Scan, and Overwrite keeps only the latest Scan's. |
The remaining settings, Maximum Source Examples per Anomaly and Maximum Record Anomalies per Check, are edited on the datastore's settings; every setting is explained on How Enrichment Works.
Steps
There are two ways to open the Enrichment Destination dialog: from the datastore's settings menu, or from the tree footer. The tabs below walk through each; pick the one you want to follow. Each field is described in the Field reference above.
Side Effects
Linking enables Scan, Materialize, and datastore Export to write to the destination. With Sync and profile the enrichment destination enabled, Qualytics also discovers and profiles the written outputs automatically. For storage impact and remediation strategies, see How Enrichment Works.
Step 1: Navigate to the Overview page of the datastore you want to link.
Step 2: Click the Settings button at the top-right corner.
Step 3: Click Enrichment in the dropdown menu.
Step 4: The Enrichment Destination dialog appears.
Step 5: Fill in the Prefix field. Qualytics uses it for Scan, Remediation, and Materialize output names, so each datastore sharing a destination needs its own.
Step 6: Choose Use existing to pick a datastore that exists, or Add new to create one.
Step 7: With Use existing, select the destination from the dropdown. A Details block appears with its Teams, Host, Database, and Schema (the URI and Root Path for file-based connectors). With Add new, select a connector, fill in its connection fields or reuse a saved connection, enter the new datastore's Name and Teams, and click Test connection.
Step 8: Leave Sync and profile the enrichment destination on unless you want to sync the destination yourself.
Step 9: Choose the Remediation Strategy: None writes no snapshot of the anomalous records (default), Append adds them after each Scan, and Overwrite keeps only the latest Scan's.
Step 10: Click Save. A success message confirms that the datastore has been updated.
Step 1: Navigate to the Overview page of the datastore you want to link. The tree view on the left selects it.
Step 2: In the footer panel below the tree, find the Writes enrichment to section showing None configured and click the Choose where enrichment is written button.
Step 3: The Enrichment Destination dialog appears.
Step 4: Fill in the Prefix field. Qualytics uses it for Scan, Remediation, and Materialize output names, so each datastore sharing a destination needs its own.
Step 5: Choose Use existing to pick a datastore that exists, or Add new to create one.
Step 6: With Use existing, select the destination from the dropdown. A Details block appears with its Teams, Host, Database, and Schema (the URI and Root Path for file-based connectors). With Add new, select a connector, fill in its connection fields or reuse a saved connection, enter the new datastore's Name and Teams, and click Test connection.
Step 7: Leave Sync and profile the enrichment destination on unless you want to sync the destination yourself.
Step 8: Choose the Remediation Strategy: None writes no snapshot of the anomalous records (default), Append adds them after each Scan, and Overwrite keeps only the latest Scan's.
Step 9: Click Save. A success message confirms that the datastore has been updated.
Once linked, the footer panel reads Writes enrichment to followed by the destination, with a button to open it.
Change the destination
To move the datastore to a different destination, there is no need to unlink first.
Step 1: Open the Enrichment Destination dialog from Settings > Enrichment . The current destination is selected.
Step 2: Under Use existing, select another destination from the dropdown.
Step 3: Click Save. A success message confirms that the datastore has been updated. Outputs already written stay in the previous destination; the next write goes to the new one.
Unlink an Enrichment Destination
To remove the link, see the Unlink an Enrichment Destination documentation.