When a client was looking for a way to unify data stored in Dynamics 365 Finance and Operations and their CRM, the new Dual-write feature was the obvious solution. This out-of-box infrastructure allows seamless interactions between ERP and CRM apps, made possible through bidirectional integration between Dynamics 365 Finance and Operations and the Common Data Service.
Aside from being able to address the immediate request of the client, the feature also promises a number of benefits for any organisation that utilises an ERP.
First of all, its near-real-time and bidirectional integration makes Dynamics 365 an all-in-one business solution. Writing little-to-no code, users can also allow all important data and the IoT (internet of things) to automatically flow to the Common Data Service. This is especially beneficial for those wanting Power Platform expansions.
Since it’s relatively new and there’s still much to explore, working with Dual-write was certainly fulfilling. However, it was not without its challenges due to the lack of documentation. Luckily, I was able to learn a couple of tips along the way to make it easier for the next person. Here are those tips.
Understand how entities behave in Dynamics 365 Finance and Operations
Before you think about syncing through Dual-write, you have to understand how entities behave in Dynamics 365 Finance and Operations. It’s easy to match and map entities with similar names in Dynamics 365 Finance and Operations and your CRM, but it’s a whole different story when you get to actually configure the entity mappings on Dual-write.
Since Dynamics 365 Finance and Operations is an ERP system, its entities are usually part of a bigger process. This means any back-end processes like customisations or data syncs can impact another process. Once a prospect entity match is made between a CRM entity and a Finance and Operations entity, try to test out how the latter works out-of-box first. This is so you’ll know how it should behave once you run the Dual-write sync.