Improved reliability of cascading changes
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Power Platform product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | Early access | General availability |
|---|---|---|---|
| Admins, makers, or analysts, automatically | - |  Sep 9, 2019 |
Oct 28, 2019 |
Business value
By moving cascading (assign, delete) jobs into the background, users will be able to resume interaction with the application sooner with fewer timeouts. Large volume cascading changes will have a higher success rate with fewer database timeouts. Long-running cascade jobs will no longer block other processes from being executed.
Feature details
Cascading changes (assign, delete) that affect more than 100 records will be processed in the background asynchronously. This allows users to resume interaction with the UI sooner and reduces UI and database timeouts when processing cascading changes. Processing these changes in the background allows for a higher rate of success when large numbers of records are involved and prevents the changes from blocking other processes that are being run on the system.
There will be a delay between when the initial change is made and when all records have been processed. The delay duration will be based on the number of records processed. The status of the background processing can be viewed in the Settings for the organization using the Jobs list.
Note
At preview this feature will only support asynchronous processing of Assign and Delete, however, by October 2019 all cascading changes will be asynchronous.
See also
Feature exploration (video)
Asynchronous cascading (docs)