MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
DynamicsMissingKeyColumns

What does this error mean?

An ADF upsert or update against Dynamics 365/Dataverse failed because required key columns are not included in the column mapping.

Common causes

  • 1The copy activity is configured for upsert/update but the primary key column (e.g., entity ID GUID) is not mapped
  • 2An alternate key was configured for upsert but the alternate key columns are not included in the source data or mapping

How to fix it

  1. 1Add the entity primary key or alternate key columns to the copy activity column mapping.
  2. 2Verify the key column values in the source data are not null — upsert key columns must have values.
  3. 3If using an alternate key for upsert, confirm the alternate key is enabled and active in Dataverse.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-dynamics-dataverse

Other data source errors