MetricSign
EN|NLRequest Access
Medium severitydata source

Power BI Refresh Error:
DynamicsPrimaryKeyMustBeGuid

What does this error mean?

The primary key being written to Dynamics 365/Dataverse is not a valid GUID — entity primary keys must be valid GUIDs.

Common causes

  • 1The source data's primary key column contains non-GUID values (integers, strings, etc.)
  • 2The GUID format in the source data is incorrect (missing hyphens, wrong length)
  • 3A column that is not the GUID primary key was mistakenly mapped to the Dynamics ID field

How to fix it

  1. 1Verify that the source column mapped to the Dynamics entity ID contains valid GUIDs.
  2. 2If the source system uses integer IDs, generate GUIDs for new records or use a lookup to find existing Dynamics record GUIDs.
  3. 3Add a data flow transformation to validate or convert source IDs to proper GUID format before the Dynamics copy.

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