K Knowledge Base
Breadcrumbs

Synchronising KDQ Results to K

When KDQ checks run, the results can be pushed directly into the K platform — making data quality outcomes visible on each asset's Data Profile Page, alongside lineage, usage, and ownership context. This is one of K's most powerful integrations: it means data consumers and governance managers can see DQ health without ever leaving K.


What Gets Synced

When KDQ results are synchronised to K, the following information is surfaced on the relevant Data Profile Page in K:

Synced Data

Where it appears in K

Overall DQ score for the asset

Data Profile Page → Data Quality tab

Pass / Fail status per check

Data Quality tab → Check detail view

Check run history and trends

Data Quality tab → Trend view

DQ issues (failing checks)

Issues tab on the Data Profile Page

DQ summary across the estate

Dashboards and Insights → Data Quality Dashboard


Prerequisites

Before syncing results, make sure:

  • At least one KDQ Workspace has been created and checks have run successfully

  • You have KDQ Workspace Admin or KDQ Platform Admin access

  • Your K platform instance has been configured to accept KDQ result ingestion (contact your KADA administrator if you are unsure)


How to Configure the Sync

Step 1 — Navigate to Workspace Settings

Within your KDQ Workspace, go to SettingsK Integration.

Step 2 — Enable the sync

Toggle Sync results to K to On.

Step 3 — Map your assets

KDQ will attempt to automatically match checks to the corresponding data assets already catalogued in K, based on the source, schema, and table/column name. Review the mapping and resolve any unmatched checks manually.

Mapping Status

Meaning

✅ Matched

KDQ has found the corresponding asset in K — results will sync automatically

⚠️ Unmatched

No matching asset was found in K — check that the source is connected and assets are catalogued

🔒 Excluded

This check has been explicitly excluded from syncing

Step 4 — Set the sync frequency

Choose how frequently results are pushed to K:

  • After each check run — Results sync in near real-time immediately after a check completes

  • Daily — Results are batched and synced once per day

  • Manual — Sync is triggered manually from the Workspace settings

Step 5 — Save and test

Click Save, then click Run Sync Now to confirm results appear correctly in K.


Viewing Synced Results in K

Once sync is active, navigate to any catalogued data asset in K that has associated DQ checks. Open the Data Quality tab on the Data Profile Page to see:

  • The current DQ score and status

  • A breakdown of individual checks (name, status, last run time)

  • A trend chart showing how DQ has changed over time

  • Links back to the originating KDQ Workspace for full detail

Failing checks will also appear as Issues on the asset, making them visible to data consumers and governance managers.


DQ Results in the Governance Dashboard

Across the K platform, aggregated KDQ results feed into the Data Quality Dashboard within Dashboards and Insights. This allows governance managers and data managers to:

  • View DQ health across the entire data estate

  • Drill down by domain, collection, source, or DQ tool

  • Identify assets with consistently failing checks

  • Prioritise remediation efforts based on usage and criticality


Troubleshooting

Issue

Likely cause

Resolution

Results not appearing in K after sync

Asset not yet catalogued in K

Ensure the source is connected and a metadata load has run

Check shows as unmatched

Name mismatch between KDQ and K

Manually map the check to the correct asset in the mapping screen

DQ tab missing on a Data Profile Page

Sync not yet configured for this Workspace

Enable the K Integration in Workspace Settings

Results appear delayed

Sync set to Daily frequency

Change sync frequency to "After each check run" for near real-time updates


💡 Tip: To ensure the K platform has the data assets catalogued before syncing, confirm your source integration has run successfully first. See KDQ Connections for details on connecting to data sources.