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
- 1Verify that the source column mapped to the Dynamics entity ID contains valid GUIDs.
- 2If the source system uses integer IDs, generate GUIDs for new records or use a lookup to find existing Dynamics record GUIDs.
- 3Add a data flow transformation to validate or convert source IDs to proper GUID format before the Dynamics copy.
Frequently asked questions
Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-dynamics-dataverse