You’re offline. This is a read only version of the page.
47
Starting this morning, users are getting the following message when merging contact records in Dynamics 365. The records are merging as expected, but I haven't seen this message before and would like to understand why we are getting this now.
All,
If you still want to use the async merging - which can seem quicker for users, I did release a fix whilst waiting for Microsoft to release.
It's fully open source if you want to see what it's changing.
Thanks,
Matt
Hello Russel,
We are able to find that configuration on a FCB.Editor and to have access to that solution I suggest you to open a Support Case with Microsoft in case you would like to apply it.
If this answer was helpful to you please mark it as an answer. Thank you!
Thank you for using Microsoft Dynamics CRM Communities.
Cláudia Amaral
Support Engineer
Microsoft Dynamics CRM
Hi, we have same problem. I understand the reason why change it to asynchronous, my suggestion is, is it possible to provide email notification after merge done, just like the settings of bulk delete operation?
Claudia,
Thanks for the response. Can you let me know how/where I would flip the FCB.EnableAsyncMergeAPI? I'm not aware where these types of configurations are made, so any help there is much appreciated.
Starting on build 9.1.0000.20463, cascade merge transactions have been moved from synchronous to asynchronous. The customer facing communication about this change can be found in the following blog:
With many large merges, they run just long enough for the UI to timeout, with most of the longest operations taking 10 minutes based on the telemetry analyzed. This change allows the merges to run in the background so that they will complete instead of getting the UI timeout.
Additional enhancements are also being discussed based on initial customer feedback on the change. There will be more to come on this as development continues.
One thing to keep in mind too is that if the asynchronous merge is really something the customer doesn’t want for whatever reason, you should be able to flip FCB.EnableAsyncMergeAPI to turn it off. It could then just be turned back on for the merges that timeout to complete them in the background when needed.
If this answer was helpful to you please mark it as an answer. Thank you!
Thank you for using Microsoft Dynamics CRM Communities.
Cláudia Amaral
Support Engineer
Microsoft Dynamics CRM
Thank you all for details. Does this mean we have to restrict the number of records being merged at one time?
I've added an item to Ideas for this. Please consider voting for it: experience.dynamics.com/.../
Please feed back to the development team that this is not a helpful change.
Most end-users don’t know or care what asynchronous processing or cascading transactions means.
Moreover, they want to see the result of whether the merge worked or not without having to go to another area (system jobs) that they rarely use.
Can we please go back to the old behaviour or at least make it a configurable setting at the org level?
This shift to asynchronous processing of merge system jobs causes a lot of our merge jobs to fail when the records have different parent records. There is a confirmation dialog that normally appears in this situation, but it does not appear when it now runs asynchronously. Users cannot interact with this dialog so our merge jobs are consistently failing. Is there a way around this?
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,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (