Alternate Key Design Between F&O and Customer Service

(0) Share

Report

Posted on by CU14051359-0

Hi everyone,

I'm currently working with Dual-write to synchronize contact information from Finance and Operations (F&O) into Dynamics 365 Customer Service.

We are facing challenges related to alternate keys. Since a single customer in F&O can have multiple identifiers (such as Account Number and Contact Person ID), the synchronization sometimes results in multiple records with seemingly identical data in Dataverse. Additionally, many customers do not have an email address, which makes it difficult to design a robust alternate key strategy.

While it is possible to change key values on the F&O side, we've found that it's not possible to edit or delete existing alternate key definitions on the Dataverse side, which limits our ability to adjust the design after initial deployment.

If anyone has experience with similar scenarios or suggestions on best practices for handling alternate keys in Dual-write, your insights would be greatly appreciated.

Thank you in advance for your support!

Best regards,

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Jonas "Jones" Melgaard 4,894 Super User 2025 Season 2 on at

Like (1)

Report

Alternate Key Design Between F&O and Customer Service

What do you mean exactly by not being able to edit keys on the Dataverse side?

It is correct, you cannot edit keys in a managed solution, but you are able to define your own keys.

Have you installed any of the orchestration packages? It should contain the mappings out of the box, and additional fields needed in Dataverse, such as a reference to the company table for entities that are per legal entity such as customers and vendors.

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/separated-solutions

Was this reply helpful? Yes No
CU14051359-0 3 on at

Like (0)

Report

Alternate Key Design Between F&O and Customer Service

@Jonas "Jones" Melgaard,

Thank you very much for your response.

When I mentioned the Dataverse side, I was referring specifically to the managed keys.
I attempted to create a new key to align with the structure on the Finance and Operations side, but unfortunately the key's status became Failed and it could not be used.

We have already imported the solution into the Finance and Operations environment, and Dual-write itself is functioning correctly.

Was this reply helpful? Yes No