Dynamics Community Forum Thread Details

Dual write for read-only entities to Dataverse

I am attempting to sync some entities (that have a read-only mode set one in SSMS) into Dataverse (using dual-write) but they do not seem to update when changes are made in Finance and Operations after the initial sync from Finance and Operations to Dataverse.

Is it common for read-only entities to not sync into Dataverse after the initial sync has been configured?

I have looked into some articles and found the below - and wanted to know whether it is relevant to my issue.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/dual-write-troubleshooting-live-sync#data-from-finance-and-operations-apps-isnt-synced-to-dataverse

The above link says:

During live synchronization, you might encounter an issue where only part of the data is synced from finance and operations apps to Dataverse, or data isn't synced at all.

Note

You must fix this issue during development.

Before you start to fix the issue, review the following prerequisites:

Make sure that your custom changes are written in a single transaction scope.
Business events and the dual-write framework don't handle doinsert(), doUpdate(), and recordset() operations, or records where skipBusinessEvents(true) is marked. If your code is inside these functions, dual-write won't be triggered.
Business events must be registered for the data source that is mapped. Some data sources might use an outer join and might be marked as read only in finance and operations apps. These data sources aren't tracked.
Changes are triggered only if the modifications are on the mapped fields. Unmapped field modifications won't trigger dual-write.
Make sure that filter evaluations provide a valid result.

Quick Links