DualWrite Filtering

Dynamics 365 ERP - Development

The article discusses the implementation of DualWrite with a customer, highlighting the challenge of dealing with data in both CRM and FnO.
A specific example is given where a single contact is used in multiple companies as an EDI address, leading to duplicates in the Global Address Book.
The contacts are synced using DualWrite to CRM, causing frustration among CRM colleagues who find the contact irrelevant.
The author was asked to create a filter to address this issue, setting the field "Profession" in FnO to EDI and adding filters for Customer Contacts in DualWrite.
The filter criteria for FnO and CRM sides are different, with the author using the post to document the syntax for future reference.
The syntax for FnO includes (AssociatedContactType = 0) && (EMPLOYMENTPROFESSION != “EDI”), while the syntax for CRM includes msdyn_contactfor eq ‘Customer’ and msdyn_sellable eq false and msdyn_contactpersonid ne null and jobtitle ne ‘EDI’.
The main reason for writing the post was to document the syntax differences and provide a reference point for similar challenges in the future.
The article also includes a link to further information on the topic for readers to explore.

Registered users can view the full text for FREE!