Dual Write

  • Article

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Note

These release notes describe functionality that may not have been released yet. To see when this functionality is planned to release, please review What’s new and planned for Common Data Model and Data Integration. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy).

Customers should be able to adopt business applications from Microsoft and expect they speak the same language and seamlessly work together. Dual Write allows our customers to not think about these apps as different systems to write to independently; rather, the underlying infrastructure makes it seamless for these apps to write simultaneously.

Frictionless experience that enables Dynamics 365 for Finance and Operations customers to natively get their data in Common Data Service

With a few clicks, customers will be able to seamlessly link to Common Data Service from Dynamics 365 for Finance and Operations. Changes in Dynamics 365 for Finance and Operations will propagate to Common Data Service and vice versa without much configuration. We will support a subset of entities at first and will grow this over time.

Optionally, Dynamics 365 for Finance and Operations admins will be able to use an advanced version of the setup in which they can customize entities and field mappings and also do source data filtering and transformation.

Ability to write initial data prior to turning on Dual Write

With this feature, we will write data that exists prior to turning on Dual Write, and keep this data updated.

Making Dual Write resilient to planned or unplanned maintenance

If data writes fail, administrators want to be notified and empowered to take action immediately. This feature provides administrators with additional capabilities to define the experiences that suit their organization's needs.

Administrators will be able to define rules that provide email notifications and/or take actions on their behalf for specific error types and thresholds. This also provides the functionality to switch to async mode in case of unexpected failures.

Dynamics 365 for Finance and Operations allows certain data to be striped by Legal Entity (LE). Each legal entity has its own customers. Products may be released per company while prices may be defined per legal entity for a customer.

While integrating data from Dynamics 365 for Finance and Operations, the appropriate products and prices must be sent to Common Data Service while ensuring visibility to the right users.

Similarly, opportunities in Common Data Service need to be created in the appropriate legal entity in Dynamics 365 for Finance and Operations.

While workarounds exist, there is a need to provide out-of-box support for multiple legal entities. With this feature, you will be able to use the same project across multiple legal entities.