54
This applies to multiple Dynamics 365 products.
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?
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?
STATUS DETAILS
Under Review
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.