The Dual Write implementation - Part 2 - understand and action pre-requisites

Prior linking environments (D365 FinOps and CDS) for dual write integration, let's work on what are the pre-requisites for this bi-directional integration from D365 FinOps to CDS or vice versa.

Check all these steps are passed and marked checklist

Follow these steps to link environment (all these steps are detailed at here).

Go to D365 FinOps | Data Management workspace | Dual-write

Click New link to environment

Choose CDS environment to link with D365 Finops, CDS environment has to be on same tenant and your user must have been added as an admin as have seen in Part 1

Select available list of Legal Entities from D365 FinOps. These can be filtered as shown below for selection.

Health check confirms all pre-requisites are installed/configured

Setup Application users in D365 FinOps and CDS (CE environment) - But why ?

"The reason for that is because the dual write technology is tightly coupled, Synchronous engine and what that means is that the data or the integration have a direct connection between the two system. So for example, FinOps when it needs to send data, it send the data to CDS using direct connection. What you need to do is to create some application users on each application side to allow those incoming connections."

Those being setup and detailed in Part 1 of this blog series

There are two application ids being added to Azure Active Directory application screen.

 

1. One application user is for incoming connections from the data integrator side

2. One is for incoming connection from my CDS instance

Why data integrator side on the incoming connection?

When initial write happens, the initial write is nothing but a hidden data integrator project, an initial sync mode or an initial write mode is we have incoming connection from the data integrator to D365 Finance and Operations.

Once you are in live sync (running state) mode then connection would be incoming from CDS instance.

This is why you need application users for two different type of connections.

P.S. You also need a similar setup in your CDS instance.

Two Dual Write solutions and Two Aspects

Dual write has two aspects

Think about Dual Write is not just he infrastructure framework like you are configuring it and using it and then you are going to get data from left to right.

1. The infrastructure is providing you near real time experience with live sync of data
2. The application side of things we really need to have OTB experience so you do need to develop something that just an easy configuration at the end.

Two dual write solutions have to be installed in the CDS environment, as installed and detailed in Part 1.  

1. The Dual-write Core Solution is focus on the infrastructure capabilities at the solution awareness for the dual write maps

2. The Dual-write Orchestration Solution includes all OTB entities and mappings that MS has shipped as part of Dual-write

This is available with name Dynamics 365 Finance and Operations Dual Write Entity Maps.

Once applied to the environment it creates all Out of the box entity maps and will look like as follows.

Click Apply Solution and choose Dynamics 365 Finance and Operations Dual Write Entity Maps solution

After the solution is being applied, the first screen will appear will look like this

Stay tune, will continue with next steps in next post.