Skip to main content

Tips and Tricks on how to validate your dual-write integration field-by-field level - its easy believe me 😊

After you are done with your entity field mappings for a required entity map e.g. for Vendor Groups, we started to look at in previous post to get the payload for dual-write integration, two records get created in the following tables.

1. DualWriteProjectConfiguration

2. DualWriteProjectFieldConfiguration

Records only get created when you Run the entity map and get deleted once you stopped it.

DualWriteProjectConfiguration table does not hold data for Vendor groups when the entity map is stopped.







DualWriteProjectFieldConfiguration table does not hold data for Vendor groups when the entity map is stopped.





Run the entity map and check data in these tables,



 




1. Both tables link each other using Name field

2. For each entity map (e.g. Vendor groups) there are two records; one for Insert and Update and the other one is for delete which ends with _end

Import information about DualWriteProjectConfiguration table:

1. External URL field holds the CDS environment's URL which is linked with FO in this format https://<CDS environment URL>/api/data/v9.0/msdyn_vendorgroups. This API URL can be browsed to see available data in CDS environment

2. Project partition map field holds list of legal entities linked for dual-write, you can copy this list in notepad++ (or any where) and check all legal entities from there too - this may help you in troubleshooting

3. IsDebugMod field if marked then failure records are stored in DualWriteErrorLog table

4. Filter query expression field if you have defined Finance and Operations apps filter for entity maps it stores here

Import information about DualWriteProjectFieldConfiguration table:

Filter records from this table based on the project name you have retrieved from DualWriteProjectConfiguration table as shown below as an example

1. External lookup urls field holds information how different lookups from CDS tables are linked for this integration.

Trick and Tip: Copy data from this field and paste into Notepad ++, data looks like this







Format JSON and you can review all data easily in JSON viewer








2. Field mapping field holds information on how fields are mapped between both apps (Finance Operations app and Common Data Service)

Trick and Tip: Copy data from this field and paste into Notepad ++, Format JSON and it shows like this

















DualWriteProjectConfigurationEntity data entity is the triggering point to sync data across based on pre-defined sync direction as discussed above.

In case you want to debug outbound call for vendor groups this will be the stack trace.












I hope this may have helped you to understand the tables and classed behind dual-write and troubleshoot your issue at some point. If you still have any question please reach out to me via comments section.

Comments

Post a Comment

I will appreciate your comments !

Popular posts from this blog

D365O - How to add financial dimension in grid

This post outlines the steps; how to add financial dimensions (segmented control) in a grid in D365O. Let's assume we are adding new table and form for below explanation; New table contains two fields  AccountType and  LedgerDimension with relation to DimensionAttributeValueCombination table  Form looks like this; Set properties for segmented control under form design; - Auto declaration = Yes - Account type field = AccountType - Controller class = DimensionDynamicAccountController - Filter expression = %1 1. Override modified method for LedgerDimension field under form's datasource 2. Override lookup and checkUserCustomLookup method on ledger dimension segmented control in form desgin Datasource | D365O_FinancialDimension | LedgerDimension | modified [DataSource]     class D365O_FinancialDimension     { ...
50 comments
Read more

The Dual Write implementation - Part 1 - Understand and Setup

What is Dual-write? Tightly couples – complete at one transaction level Near real time Bi-directional Master data and business documents – Customer records you are creating and modifying and at this document we are talking about sales orders or quotes and invoice. Master data could be reference data e.g. customer groups and tax information Why Dual-write and why not Data Integrator? Data Integrator is Manual or Scheduled One directional Now, Let's deep dive and understand what is required for Dual-write setup and from where to start. First thing first, check you have access to https://make.powerapps.com/ Choose right environment of CDS (CE) Make sure you have access to the environment too, click on gear icon and Admin Center  Look for required environment and Open it, you must have access as going forward you are going to configure dual write steps in the environment user the same user you are logged in now. Now, go back to power platform admin center and...
57 comments
Read more

Another step closer - Finance Operations data in Power Platform - Virtual Entities

This post focuses on the integration technologies available to have the Microsoft Dynamics 365 Finance Operations data available in Dataverse/Common Data Services/CDS. What could be better then having The biggest ERP system's data in Power Platform. You can Power Portals, Power Apps, Power BI analytical reports, use power virtual agents for inventory closing and year end closing processes, manage expenses and employee/contractors time entry processes, most of these processes can be even without logging to MS ERP (Dynamics 365 Finance Operation) so can safe on license cost too.  Let's see what options are available to integrate F&O data with Power Platform however, this post is dedicated to Virtual Entities.  3 Options available out-the-box to integrate F&O data with Power Platform; 👉  Data Integrator  - Click on link to read more 👉  Dual-Write  -  Click on link to read more 👉  Virtual Entities - MS Tech Talk on Virtual entities   ...
71 comments
Read more