Dualwrite tips and tricks

Development Guide

Dual Write

 

1. Prerequisites 

1. Finance and Operations apps that have build version 10.0.9 (10.0.383.20013) (Quality update) and platform update 33 or later

2. Model-driven apps in Microsoft Dynamics 365 that have platform version 9.1.0000.11732 or later

2. Entity Creation

I’m assuming that you have already setup and configured Dual-Write in your D365 FO and Dataverse (CDS) environments. Furthermore, required entities are already created in FO and Dataverse (CDS) applications and fields are also added as per the following data type mappings.

MS D365 FO Field Type	MS Dataverse Field Type
String	Text
String (Memo)	Text (Multiline)
Base Enum	Choices
Boolean	Yes/No
Integer / Real	Decimal
Date	Date Only
Date Time	Date and Time

3. Create Integration Key

It is very important to properly create and configure table key in MS Dataverse as per F&O entity key to avoid below error during mapping.

Mapping is missing for integration key - Requisition Number

Following are the steps to create that key in MS Dataverse.

1. First, open Finance and Operations development environment.

2. Open Visual Studio.

3. In Application Explorer, Go to Data Model > Data Entities > Open [Your Entity] in designer.

4. Expand Keys > EntityKey > [Your Key].

                                                        F&O Data Entity Key

5. Now, go to https://make.powerapps.com/, select target Environment.

6. Go to Solutions.

7. Open any Unmanaged Solution, create one if you don't have.

8. Open your entity (User information in my case).

9. Go to Keys tab.

10. Click on +Add Key and Select UserId field.

MS Dataverse Solution

User Information Table

Note: Key fields of both FO Entity and Dataverse Table must be mapped to each other.

4. Dual Write Entity/Table Mapping

Following are the steps to create mapping between Dataverse table and F&O entity through dual write. 

1. Open your Finance and Operations application.

2. Go to Data management workspace.

3. Click on Dual Write Title.

4. Click on +Add Table Map.

5. Select F&O Entity and Dataverse Table.

6. Hit Save.

5. Dual Write Field Mapping

In this section, we’ll go through the steps and tricks that will be required to map Dataverse columns to Finance and Operation app fields through dual write workspace.

1. Click on Entity from Dual Write entity list.

                        


                        

2. By clicking +Add Mapping button, you can create the following types of mappings

1. Base Enum to Choices

To create such mappings, the following  transformation needs to be defined.

1. Get F&O Base Enum Values.

1. Open Finance and Operations development environm

2. ent.Open Visual Studio.

3. In Application Explorer, Go to Data Model > Data Entities > Open SystemUserEntity (or Any Entity) entity in designer.

4. Under Fields, right click on EVENTPOPDISPLAYWHEN (or Any Field) field and go to it’s base EDT.

2. Get Dataverse Choices Values.

1. Go to https://make.powerapps.com/, select target Environment.

2. Open your User information (or Any Entity) entity.

3. Under Columns, open Event PopUp Display When (or Any Column) column.

4. Click on Edit Choices button.

5. Get Choices Values like below

6. 
   

 

Note: Make sure to remove commas from values. like 810,780,000 should be 810780000

2. NoYesId to Yes/No

To create mapping between Boolean and Yes/No type fields, please follow the below transformation.

3. General Mapping

No transformation will be required for all other types of mappings. Create such mappings simply by using “ = ” operator as below. 

6. Sync Data

Please follow the steps to sync data between MS Finance And Operations and MS Dataverse applications to test above mappings.

1. Open the Finance and Operations app and go to Data Management > Dual-write.

2. Run the Initial sync functionality for the tables that you want to sync data for.

7. Helpful Links

1. Considerations for initial synchronization.

2. Troubleshoot issues during initial synchronization.

3. Enable table map for Dual Write.

4. Dual-write integration for Cross-Company data

5. Tips for Dual Writ Integration.