Forum Discussion
Error while trying to load data from my lakehouse to Dataverse
Hello Team,
I'm currently trying to load data from a Lakehouse table into a Dataverse table using a pipeline copy activity. While this isn't my preferred solution, it was the only method I found to load data directly into Dataverse.
I encountered the following error:
Here's below the mapping i actually use for this, is it probably due to having two GUID fields ?
This error does not occur when loading other tables, so it appears to be specific to this dataset or configuration.
Has anyone experienced something similar or have suggestions on how to resolve this? Any guidance would be greatly appreciated.
Thank you for your help!
Hi ABSOmar , Thank you for reaching out to the Microsoft Community Forum.
This error is not because of having two GUID fields and it is also not a simple string-to-GUID formatting issue. The copy activity is reaching Dataverse successfully, which means the GUID values are being parsed correctly. The failure happens when Dataverse tries to resolve one of those GUIDs as a lookup reference and cannot find the referenced record.
In your mapping, fields like brz_role (and potentially brz_mdrmappingid) are lookup columns in Dataverse, not plain GUID fields. For lookup columns, Dataverse requires that the GUID already exists in the target entity the lookup points to. If even a single row contains a GUID that does not exist or belongs to a different entity than the lookup expects, Dataverse rejects the entire operation with the exact error you are seeing. This also explains why other tables load fine and only this dataset fails.
Verify that every GUID you are sending into lookup fields actually exists in Dataverse and refers to the correct table. If these values are just business identifiers and not Dataverse record IDs, you will need to load or resolve the referenced records first (or use alternate keys) or change the column to a non lookup field if a relationship is not required.
4 Replies
Hi ABSOmar , Thank you for reaching out to the Microsoft Community Forum.
This error is not because of having two GUID fields and it is also not a simple string-to-GUID formatting issue. The copy activity is reaching Dataverse successfully, which means the GUID values are being parsed correctly. The failure happens when Dataverse tries to resolve one of those GUIDs as a lookup reference and cannot find the referenced record.
In your mapping, fields like brz_role (and potentially brz_mdrmappingid) are lookup columns in Dataverse, not plain GUID fields. For lookup columns, Dataverse requires that the GUID already exists in the target entity the lookup points to. If even a single row contains a GUID that does not exist or belongs to a different entity than the lookup expects, Dataverse rejects the entire operation with the exact error you are seeing. This also explains why other tables load fine and only this dataset fails.
Verify that every GUID you are sending into lookup fields actually exists in Dataverse and refers to the correct table. If these values are just business identifiers and not Dataverse record IDs, you will need to load or resolve the referenced records first (or use alternate keys) or change the column to a non lookup field if a relationship is not required.
Hello v-hashadapu,
Indeed ! the value wasn't on my destination table, thank you for helping to resolve,
Hi ABSOmar
I can see you source data type is String. If you are converting from String make sure you check these -
- The string must represent a valid GUID:
- 32 hexadecimal characters
- Hyphenated format (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) or compact format without hyphens
- No extra spaces or invalid characters
- If any value is not a valid GUID, the copy job will fail with a type conversion error.
These are the common pitfalls in converting from String to GUID
- Empty or null strings → must be handled (either filtered out or replaced with null).
- Incorrect format → e.g., missing hyphens, uppercase/lowercase is fine, but letters outside A-F or wrong length will fail.
Hope this helps - please appreciate leaving a Kudos or accepting as a Solution!
- The string must represent a valid GUID:
