Dual-write Architecture
In Integrated with ERP scenarios, Project Operations uses dual-write to synchronise data between Dataverse and Dynamics 365 Finance. Dual-write is not just plumbing: it affects ownership, recovery, audit evidence and reconciliation.
Conceptual flow
What to verify
| Area | Evidence |
|---|---|
| Prerequisites | Required Dataverse apps, Finance solutions, entity refresh and map installation evidence. |
| Map versions | Installed Project Operations maps, versions, customisations and disabled maps. |
| Ownership | Which records are created in Dataverse, enriched in Finance or synchronised both ways. |
| Errors | Dual-write errors, failed initial sync, stuck records and business validation failures. |
| Reconciliation | Integration workspace evidence, actuals reconciliation and trial balance implications. |
| Recovery | Supported retry, resynchronisation, correction or compensation route. |
Map health is engagement evidence
Do not treat map errors as operational noise during an assessment. They may explain missing actuals, unmatched transaction connections, invoice issues or financial reconciliation differences.
Primary Microsoft documentation
- Project Operations dual-write integration overview
- Manually deploy the Project Operations Dataverse app with dual-write support
- Project Operations setup and configuration data integration
- Install Project Operations dual-write map versions
- Project Operations integration workspace
- Use actuals synchronization and reconciliation