News and Announcements icon

Dynamics 365 CommunityForums Finance forum Dual write creates dup...

Finance forum

Suggested answer

Dual write creates duplicate records

(0) Share

Report

Report

Posted on by CU30040608-0

175

Hi,

I have created a custom table in FO and a matching table in DataVerse. I have then configured dual-write for the tables going from FO to dataverse.

For the integration key in FO i have choosen Name because this should be unique.

My problem:

If i edit the Name value in FO the name is not updated in dataverse. Instead a new record with the same data is created. I guess this is because i am editing the integration key.

Is this normal behavior? What is the best practice?

Categories:

Development / Customization / SDK

All responses Img

All responses (2)

Answers Img

Answers (0)

Suggested answer

Komi Siabi 12,494 Most Valuable Professional on at

Like (0)

Report

Dual write creates duplicate records

Just like André said, that is expected to be the behavior.

In table design concept, it is advisable to always use and ID for your key. You would such applied most tables in FO such as VendTable, PurchTable, HcmWorker.

You should consider changing your integration key field.
Suggested answer

André Arnaud de Cal... 290,349 Super User 2024 Season 2 on at

Like (1)

Report

Dual write creates duplicate records

Hi,

This is expected behavior. The key is used to find the record in both applications. If you change the name, it will try to find a record with the same name. It will not find it and will create a new record. I would suggest using an identification field as the key that is not expected to be changed.

Helpful resources

Quick Links

Leaderboard

#1

André Arnaud de Cal... 290,349 Super User 2024 Season 2

#2

Martin Dráb 228,212 Most Valuable Professional

#3

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans