Dual Write Setup LCS

LCS, Dynamics 365, CDS

Dual-write provides data integration across Microsoft Dynamics 365 applications. This robust framework links environments and enables different business applications to work together. Here are the top reasons why you should use dual-write:

• Dual-write provides tightly coupled, near-real-time, and bidirectional integration between Finance and Operations apps and model-driven apps in Dynamics 365. This integration makes Microsoft Dynamics 365 the one-stop shop for all your business solutions. Customers who use Dynamics 365 Finance and Dynamics 365 Supply Chain Management, but who use non-Microsoft solutions for customer relationship management (CRM), are moving toward Dynamics 365 for its dual-write support.
• Data from customers, products, operations, projects, and the Internet of Things (IoT) automatically flows to Common Data Service through dual-write. This connection is very useful for businesses that are interested in Microsoft Power Platform expansions.
• The dual-write infrastructure follows the no-code/low-code principle. Minimal engineering effort is required to extend the standard table-to-table maps and to include custom maps.
• Dual-write supports both online mode and offline mode. Microsoft is the only company that offers support for online and offline modes.

Dual-write setup from LCS

I decided to write this post due to currently looking at the Dual-Write. This topic explains how to set up a dual-write connection between a new Finance and Operations environment and a new Common Data Service environment from Microsoft Dynamics Lifecycle Services (LCS).

Prerequisites

The setup of a dual-write connection has the following requirements:

• Finance and Operations apps that have build version 10.0.9 and platform update 33 or later
• Model-driven apps in Microsoft Dynamics 365 that have platform version 9.1.0000.11732 or later

You must be an admin in both FinOPs environments and CDS environments to set up a dual-write connection.

Set up a dual-write connection

Follow these steps to set up the dual-write connection.

1. In LCS, go to your project.
2. Select Configure to deploy a new environment.
3. Select the version.
4. Select the topology. If only one topology is available, it’s automatically selected.
5. Complete the first steps in the Deployment settings wizard.
6. On the Common Data Service tab, follow one of these steps:
   1. If a Common Data Service environment is already provisioned for your tenant, you can select it.

1. Set the Configure Common Data Service option to Yes.
2. In the Available environments field, select the environment to integrate with your Finance and Operations data. The list includes all environments where you have admin privileges.
3. Select the Agree check box to indicate that you agree to the terms and conditions.

• If your tenant doesn’t already have a Common Data Service environment, a new environment will be provisioned.
  • Set the Configure Common Data Service option to Yes.
  • Enter a name for the Common Data Service environment.
  • Select the region to deploy the environment in.
  • Select the default language and currency for the environment.

 Note

You can’t change the language and currency later.

• Select the Agree check box to indicate that you agree to the terms and conditions.

• Complete the remaining steps in the Deployment settings wizard.
• After the environment has a status of Deployed, open the environment details page. The Common Data Service environment information section shows the names of the Finance and Operations environment and the Common Data Service environment that are linked.

• An admin of the Finance and Operations environment must sign in to LCS and select Link to CDS for Apps to complete the link. The environment details page shows the admin’s contact information.

After the link is completed, the status is updated to Environment linking successfully completed.

1. To open the Data integration workspace in the Finance and Operations environment and control the templates that are available, select Link to CDS for Apps.

 Note

You can’t un-link environments by using LCS. To un-link an environment, open the Data integration work-space in the Finance and Operations environment, and then select Un-link.