Small and medium business | Business Central, N...

Modify Primary key value through BC-CRM Integration

(5) Share

Report

Posted on by MSD_BC_User

Hi,

I have a table in BC with the Primary key field which I want to be modified through the sync from the CRM to BC. I have created the integration table and field mappings. Records can be created in BC and CRM through the sync successfully. Updating the primary key field in BC can sync to CRM without any issue. When the BC Primary key field value in CRM is modified, it cannot be synced back to BC. Other fields can be synced without any issues from CRM to BC.

Is there anyway to force rename the primary key field when synced from CRM to BC. Modifying the primary key field is very much need for my case. Can anyone point me how to make the sync work for the primary key field?

Thanks and Regards.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Marco Mels Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hello,

What is the error in the process when synchronizing the changes back to BC. The integration table mapping probably contains a references to the original PK which can no longer be found.

Thanks.

Was this reply helpful? Yes No
Vlora 12 on at

Like (1)

Report
Copy link

Link copied!

Hi MSD_BC_Use

Please if you remember can you tell us How you solve this.

Thanks in advance

Vlora

Was this reply helpful? Yes No
FM-27032246-0 9 on at

Like (1)

Report
Copy link

Link copied!

Hi!

I am currently facing the same issue.

Did you ever manage to find a solution to this?

Thanks!

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,978 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Will recoupling update this primary key?

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,324 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

I am not sure but if this helps:https://community.dynamics.com/blogs/post/?postid=fe9e0521-f65c-4e22-997f-7dd14cc44588

Was this reply helpful? Yes No
FM-27032246-0 9 on at

Like (1)

Report
Copy link

Link copied!

@YUN ZHU

In my specific case, the primary key field is actually the one used for coupling, so I am afraid this is not a workable alternative and might be part of the problem.

This issue has come up during a cloud migration project from BC14 on-prem. Weirdly, according to our customer, and from what I have been able to find, this same integration table mapping worked without problems in BC14. Do you know if anything was fundamentally different about the integration table mappings back then, which would have allowed this to work?

An alternative idea I came up with would be to add an additional field to hold the updated id. I could then run a job which renames those records, where the PK is different to the updated value.

Was this reply helpful? Yes No