Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
Data is written in Finance and Operations (F&O) but is rolled back in Customer Engagement (CE) during dual write operations.
Reason:
This may be due to duplicate records or a primary key mismatch between F&O and CE. This discrepancy can lead to inconsistencies in data synchronization and unexpected behavior in the system. The error message indicates that “The given key was not present in the dictionary,” which suggests a potential issue with key values in the entity.
Resolution:
- Verify if this occurs in all environments. It has been noted that this does not happen in all environments, indicating it may be environment-specific.
- Check the last time the dual write operation was successful. It has been reported that the issue occurred only once, which may suggest it is intermittent.
- Identify if the issue is happening with standard or custom entities. The issue has been confirmed to occur only with a custom entity.
- Review any error messages received during the dual write process. Specific error messages should be documented for further analysis.
- Implement additional data validation checks to ensure that records are unique and primary keys are correctly assigned.
- Enhance monitoring capabilities to capture more detailed telemetry data, even for customized entities, to help identify and diagnose issues more effectively.
- Conduct regular audits of the data synchronization process to identify and rectify any discrepancies early on.
- If the problem persists, consider increasing the timeout for dual write operations, as timeout issues are common in dual write scenarios.