Problem

When creating contacts in Finance and Operations (FnO) with Dual-Write integration, certain actions fail or behave inconsistently, causing synchronization issues with Customer Engagement (CE).

This is a known issue documented here:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/party-gab#known-issues-and-limitations

Current Behavior (Errors)

• Adding a contact to a customer in FnO may fail if the party record does not exist in CE. FO sends a contact referencing a party ID that CE cannot resolve, causing an error in msdyn_contactforparties.
• Creating a new customer and adding additional contacts after the first one may fail silently without error.
• Adding multiple contacts to a newly created customer in FnO often results in only the first contact syncing; subsequent contacts fail without error.

Expected Behavior

Contact creation should work consistently across all scenarios without errors or silent failures, ensuring proper synchronization between FnO and CE.

Impact

• Disruption in customer and contact management workflows.
• Increased manual intervention and troubleshooting efforts.
• Negative effect on operational efficiency and user experience.

Request

We kindly ask Microsoft to:

1. Evaluate adding resolutions in upcoming FnO/Dual-Write updates.
2. Provide visibility in LCS or official channels for customer tracking.
3. Continue addressing this as an internally registered issue to ensure alignment with known limitations and progress toward resolution.