Error in synchronization in integration from dataverse

(2) Share

Report

Posted on by Ahsan baig 123

141

I have set up dataverse connection in business central which was a success.

However, when i am syncing customer integration from integration table mapping page, i am getting following error.

An error occurred when communicating with Dataverse.

Detailed description: Unable to cast object of type 'Microsoft.Xrm.Sdk.Entity' to type 'Microsoft.Xrm.Sdk.EntityReference'.

How this can be resolved.

Thanks

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

DAnny3211 11,369 on at

Like (0)

Report
Error in synchronization in integration from dataverse

Hi Ahsan,

Thanks for sharing the details! The error you're encountering:

"Unable to cast object of type 'Microsoft.Xrm.Sdk.Entity' to type 'Microsoft.Xrm.Sdk.EntityReference'"

typically occurs when a field in the Dataverse entity is expected to be a lookup (EntityReference) but is instead being treated as a full Entity object.

Here's how you can troubleshoot and resolve this:

Check Field Mappings:

Go to the Integration Field Mapping for the CUSTOMER table.

Look for any fields that are mapped to lookup fields in Dataverse (e.g., PrimaryContactId, OwnerId, etc.).

Ensure that these fields are correctly mapped to EntityReference types in Business Central.

Review the Target Dataverse Schema:

In Dataverse, confirm that the target field is indeed a lookup and not a complex object or collection.

If the field is a lookup, Business Central should send an EntityReference, not a full Entity.

Update or Remove Problematic Mappings:

Temporarily remove or correct the mapping for the field causing the issue.

Try syncing again to isolate the problematic field.

Use Logging and Debugging:

Enable detailed logging in Business Central to capture the exact field causing the cast error.

This can help pinpoint the mismatch.

Check for Customizations:

If your Dataverse environment has custom plugins or logic that modifies the expected data types, this could also cause the issue.

If the issue persists, consider raising a support ticket with Microsoft and include the full mapping configuration and error trace.

Hope this helps!
Please mark this response as helpful if it answered your question.

Best regards!

Was this reply helpful? Yes No