Starting in August 2020, merging records became an asynchronous operation (https://docs.microsoft.com/en-us/power-platform/admin/async-cascading)
This was not a helpful change and is making the system less efficient to use.
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?
Comments
Having this be asynchronous is a positive thing, we just need a better UI to view the progress. Use the same type of dialog as modern email that can be minimized and multiple may be hidden at the bottom of the window and status checked. It would be great if the color of the window changed based on status updates of the process, so at a glance it would be visible even minimized.
Category: Account, Contact, Calendar and Activity Management
There are also business cases where it must first be checked whether a merge can be carried out at all.
This could be done in a pre-merge plugin and in case a merge is not allowed to be executed, an exception could be thrown out of the plugin. This message was then displayed synchronously to the user.
With this change it is no longer possible to give feedback to users why a merge is not executed.
Category: Account, Contact, Calendar and Activity Management
Revathi Sankar (administrator)
Thank you for the request. We are currently working with the platform team & reviewing options to implement this idea. We will update you as we progress towards release.