Dynamics 365 Integration / Field notes
Dual-Write Identity: Keep Dataverse and F&O Records Linked
A record synchronization is only dependable when both applications can keep referring to the same business entity. In dual-write, the Dataverse integration key helps locate the corresponding row; its constituent identity fields need stable ownership and a deliberate change policy.
Separate technical IDs from business identity
Each system may generate its own internal identifier. The integration still needs a durable way to associate the rows across the boundary. Microsoft documents dual-write integration keys as natural keys based on Dataverse alternate keys; they help locate the correct row when the Finance & Operations operation starts.
List the identifiers available at the point of creation, which system owns each one and how later edits or mergers affect them. Do not use a display name as a key simply because it looks understandable to users.
Keep key fields stable
Microsoft warns that changing a column that participates in the alternate key changes the record identity and can break the relationship. Prefer fields users cannot casually edit, and define how corrections are handled if a key value must change.
The receiving integration must also handle records created before synchronization begins. Initial synchronization is a separate setup decision; decide whether existing data must be reconciled before enabling a map.
Include legal-entity scope in the design
A matching key is not enough if the Finance & Operations record belongs to the wrong company. Document the company scope of each map, who creates the original record and how company-specific behavior is represented.
Test one representative record per relevant company and verify the source and destination relationship after create, update and an attempted key correction. Keep duplicate records and unresolved map errors visible for support.
Review the handoff before enabling a map
Dual-write is a specific integration capability between finance and operations environments and Dataverse. It is not a generic connector promise for arbitrary applications. Confirm environment prerequisites, selected table maps, key fields and data ownership for the exact scenario before activation.
- Name the business record and authoritative owner
- Choose the Dataverse alternate-key fields
- Confirm key fields are stable and permitted
- Set the Finance & Operations company scope
- Reconcile existing rows if initial synchronization is needed
- Verify create, update, correction and error behavior
Primary sources
Sources and further reading.
These platform references support the technical guidance. Available features, versions and implementation requirements should be checked against your environment.