Merge Duplicates - Asynchronous Processing of Cascading Transactions

(0) Share

Report

Posted on by JRussell1738

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.

I have the same question (0)

All responses (15)

Answers (1)

Suggested answer

Claudia Amaral on at

Like (1)

Report

This behavior is expected and it's recent, that's why you are seeing it for the first time. It's only an informative message as the users should be aware of the amount of cascading of these records.

This means the change on a parent record will be transacted upon (cascade down through) all the child records.

You can track the progress on the System Jobs.

Please see this documentation: https://docs.microsoft.com/en-us/power-platform/admin/async-cascading

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

Was this reply helpful? Yes No
JRussell1738 47 on at

Like (0)

Report

Thanks for the quick response. Does this mean that all merges are now handled asynchronously, or is there something else going on with our instance that is now forcing these to be handled differently?

Was this reply helpful? Yes No
Suggested answer

Claudia Amaral on at

Like (0)

Report

Hello,

We don't have an option to change the merge operation to run synchronous in the UI. The amount of time that merge operation will take will depend of the number of concurrence requests that are running in the organization and also the relationships we have in place for the records we are merging.

To access the state of the asynchronous merge request, using the UI, we will be able to see the it in System Jobs view where the System Administrator can access.
It’s also possible to verify this programmatically by following the sample in the article
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/asynchronous-operation-states

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

Was this reply helpful? Yes No
JRussell1738 47 on at

Like (0)

Report

Claudia - Is this something that recently changed globally with Dynamics 365? We weren't getting these messages last week. Did something change with our instance of Dynamics or was a change made to force merging to an asynchronous process?

I ask because users are not seeing merged records disappear like they are used to seeing (because it's occurring in the background rather than instantly) and we've fielded a lot of questions about the change in process.

Thanks for any information you can provide.

Was this reply helpful? Yes No
Claudia Amaral on at

Like (0)

Report

Hello,

This change was automatically deployed last week.

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

Was this reply helpful? Yes No
Jonathan Blackham 30 on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Feridun Kadir 1,705 Most Valuable Professional on at

Like (1)

Report

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?

Was this reply helpful? Yes No
mdavignon 25 on at

Like (0)

Report

Our clients are also experiencing these failures now and the feedback on this change has been unanimously negative. I'm hoping this will be reconsidered.

Was this reply helpful? Yes No
Feridun Kadir 1,705 Most Valuable Professional on at

Like (0)

Report

I've added an item to Ideas for this. Please consider voting for it: experience.dynamics.com/.../

Was this reply helpful? Yes No
Roma Gupta 725 on at

Like (0)

Report

Thank you all for details. Does this mean we have to restrict the number of records being merged at one time?

Was this reply helpful? Yes No