Have you ever tried to assign an account to a new owner only to have the system lock up and timeout because you have too many child records in the cascading transaction set? A new feature is available for preview that will help reduce system timeouts when processing entity updates that use large volume cascading changes.
Currently, cascading operations are performed as a synchronous transaction. In a synchronous cascading transaction, all impacted records are identified by the system. As the records are processed, they are locked by the system. Once all the changes have been completed, the records are unlocked, and the transaction is completed. The trouble is that synchronous transactions with many records can cause performance issues for environments because long running transactions can fail due to server timeouts. Also, during these transactions, the records are locked preventing other jobs and user transactions that operate on the same records from executing. Long running transactions might result in a backlog of pending transactions and requests that decrease system performance and might cause work stoppage.
To decrease timeouts or degraded performance while cascading operations are in progress, we are changing cascading transactions from synchronous mode to asynchronous mode. For detailed information about synchronous vs. asynchronous modes and to track asynchronous operations, see the documentation at Asynchronous processing of cascading transactions
All Dynamics 365 online organizations will be migrated to asynchronous processing with the October release. There are two ways you can try it out early:
To submit your request to have your environment changed to asynchronous mode:
We hope you enjoy the newly added features and are excited to hear what you thinks about them. If you have questions or other feedback, please let us know on the PowerApps administer PowerApps forum. We look forward to hearing from you!
The post Reduce timeouts for cascading transactions appeared first on Dynamics 365 Blog.