Skip to content

Data Catalog Links FAQ

Answers to common questions about availability, manual links, unlinking, and synchronization.

Availability

Source datastores backed by a database connector (JDBC and native connectors). File-based (DFS) datastores do not offer the dialog, at any level.

No. Enrichment datastores hold the outputs Qualytics writes, such as scan results and anomaly details, which have no counterpart asset in your catalog.

No. Computed assets exist only in Qualytics, so the catalog has no counterpart for them. On fields, excluded and missing fields cannot be linked either.

No. A manual link is never overwritten by a later synchronization, and it stays valid when the integration's configuration changes. To hand the match back to the automatic synchronization, unlink the asset.

Unlink is only offered on manual links. The link you are looking at was created automatically, and removing it would be pointless, since the next synchronization would just recreate it. To replace it, use Change asset instead.

I linked the datastore manually. Do I need to fix its containers too?

Usually not. The datastore's manual link anchors how its containers and fields resolve on later synchronizations, so the children follow it. Correct an individual container or field only when that one asset still resolves wrong.

The link becomes manual, its Last Synced resets, and the next synchronization pushes the full Qualytics metadata to the newly linked asset instead of skipping it as unchanged.

Synchronization

What do Pull and Push exchange?

Pull brings supported catalog metadata into Qualytics, and Push sends Qualytics metadata to the catalog. Exactly what each direction exchanges depends on the catalog; see the Synchronization section of your catalog's own page, listed under Supported Data Catalogs.

Why is there no Sync button on a container or a field?

The synchronization scope is the datastore, so only the datastore's dialog starts one. The container and field dialogs point you to the source datastore instead.

Who can start a synchronization?

The datastore-scoped synchronization requires the Editor team permission on the datastore. The full synchronization, covering every datastore of the integration, requires the Manager or Admin role and runs from Settings > Integrations.