Dynamics 365 ERP - Development
Category
Feb 25, 2024
Published date
Text
Article Type
AI Summary
- The blog article discusses the challenges faced with the execution of Dual Write, an integration between Dynamics CRM and Dynamics Finance & SCM, and provides recommendations for reliable integration.
- One of the challenges mentioned is the limitation of Dual Write to support only 10 lookups for a table during the initial sync of the Master data between Dynamics 365 CRM and FnO.
- The installation of Dual Write core and Dual-write application orchestration solution is not compatible with certain regions, causing unavailability of the solution in those regions.
- Enabling Dual Write between Project Operations & Finance and Operations sometimes results in missing corresponding solutions in the instance, which can be addressed by requesting cab files from the PG team and waiting for them to deploy the solutions.
- Another issue mentioned is the error encountered when creating a project contract, indicating that the billing rule is missing or not updated in the contract line. It is recommended to investigate and resolve any discrepancies in the synchronization process to address this issue.
- Dual Write integration in CRM encounters errors with version mismatches for tables like quotes and sales orders, disrupting bidirectional data flow. This can be addressed by rectifying Out-of-the-Box table mappings, ensuring version alignment, and validating data values.
- Other issues mentioned include the integration of Sales Quotation OOB resulting in an extra address in D365 F&O and the inability to add an item in the released product. Workarounds and patches provided by Microsoft were mentioned for these issues.
- The article concludes with recommendations for reliable integrations, including using Azure Integration Services (AIS) or third-party integration platforms like TIBCO and Kingswaysoft.Please note that this is a summary of the article provided.
Registered users can view the full text for FREE!
Sign In Now!