44
Hello,
the native CDS/CE Integration creates multiple contacts/customers when a contact/account is synchronized from CDS to Business Central. Does anyone experience the same issue? Any suggestions?
Best regards,
Dima.
Hi Marco,
No, we didn't modify the standard filter. We also cannot switch to only coupled records, since our webshop creates hundreds of new contact/account records in CRM per day that have to be synched to BC.
Best regards,
Dima.
Hello,
I do not think it is supposed to work like this. Did you modify the standard filter within the integration table mapping? To overcome this you may want to switch on synch only coupled records (Integration table mapping).
Thanks.
Hi Greg, hi Marco,
thank you for the hints. In the meantime i could find the cause. There are 2 jobs in BC: 1 for contacts and 1 for accounts synchronization. But since a crm-contact is connected to a crm-account (parent customer), for new crm contacts the contact-job creates 3 records in BC: 1 contact of type "person", 1 contact of type "company" and 1 customer and connects the 3 records. The customer-job creates 1 customer for new crm-accounts.
The issue appears, when both the contact-job and account-job are executed simultaneously. This ends up with the contact-job creating one customer and the customer-job creating another customer for the same crm-account. We will try to bypass this problem by configuring different intervals for the job-executions. If simultaneous executions will still appear (for ex. when both jobs stop due to an error and will be restarted at the same time) we will deactivate the customer-job, since the contact-job creates all records (contacts and customers) in BC.
We know that the second solution will lead to the situation, that modifications on crm-accounts and/or bc-customers will not be synced. But at the moment we usually do not update accounts/customers. And if needed, we will sync them manually.
Best regards,
Dima.
This looks like a bug so Marco Mels probably gave you the best solution.
But sometimes there is confusion about how this works, so I would clarify one thing...
The integration does NOT try to match records that are similar and automatically couple them together. So if you have records in both systems and they need to be coupled, then you need to do that "manual" coupling before you turn on the integration.
If you only have records in one system, then there is no manual coupling needed.
Hello,
Please raise this issue to Microsoft via your partner or CSP.
Thanks.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (