Views:

Applies to Product - Dynamics 365 Supply Chain Management
 

What’s happening?
Customers are experiencing issues with Dual Write synchronization for all entities, specifically being unable to write data to entity accounts and encountering error messages related to lookup field mismatches.
 

Reason:
The underlying cause of this is related to lookup field company mismatches, where the company associated with lookup fields does not match the customer company. Additionally, there is a known limitation on FetchXML queries that causes initial sync failures when the entity mapping contains more than 10 lookup fields.
 

Resolution:

  1. Refresh Elements:
  2. Navigate to System Administration -> Setup -> Refresh Element to resolve potential cache issues.
  3. Check Lookup Fields:
  4. Ensure that all lookup fields have the same company as the master record. Specifically, check the following lookups: Customer Group, Sales Group, and Currency Code.
  5. Split Initial Sync:
  6. If the entity mapping contains more than 10 lookup fields, split the initial sync into multiple steps:
    • In the first step, remove some of the non-mandatory lookup fields from the dual-write entity map to bring the number of lookups to 10.
    • Save the map and perform the initial sync.
    • Once the initial sync for the first step is successful, add the remaining lookup fields back to the map, ensuring the total number of lookup fields remains at 10.
    • Save the map and run the initial sync again.
    • Repeat these steps until all lookup fields are successfully initial synced.
    • Finally, add all lookup fields back to the map, save it, and run the map with the option to skip initial sync to enable live sync mode.
  7. Monitor Errors:
  8. If errors persist, provide the environment details for both Finance and Operations (FO) and Customer Engagement (CE) to further investigate the Dual Write setup and mapping entity.
  9. Documentation Reference:
  10. For additional troubleshooting, refer to the documentation provided at the following link: Dual Write Troubleshooting.
  11. Alternative Key Check:
  12. Verify that the value of the alternative key in Dataverse matches the key of the data entity defined in the Finance and Operations app.
If the above steps do not resolve the issue, further investigation may be required, and it is recommended to schedule a meeting with the appropriate team for assistance.