UI Migration Stories: How to fix issues with Business Process Flow not moving automatically
ECLEVA is a Business Applications Consultancy with deep industry expertise and technical expertise. We work with clients who invest heavily in automation. This in turn means we often push the boundaries of existing technologies and in doing so discover bugs and vulnerabilities. We want to share out latest discovery with the Microsoft Community and our clients and how we have solved this in case you encounter a similar issue.
Failure to launch
For some of our clients, we have architected that their Microsoft Business Process Flow (BPF) automatically moves from one stage to another if certain conditions are met. Interestingly, when we used Xrm.Utility.openEntityForm in the classic interface to refresh forms, this script failed to work in the Unified Interface (UI). This was because Microsoft deprecated the Xrm.Utility.openEntityForm.
When users went to update CRM fields as they were used to doing using the Classic Interface, they were not able to do so in the UI. It appears that this is a specific issue related to UI and doesn’t seem to occur anywhere else when you move to UI.
To solve this, we identified that the JavaScript function to refresh the form must be changed (see below for details).
How to fix it
To fix refresh problem, we used Xrm.Navigation.openForm instead of Xrm.Utility.openEntityForm. This simple fix has resolved the issue.
Below is an example of Xrm.Navigation.openForm.
We really hope this hack helps you. If you have any MS UI story or insight to share, please leave a reply below.
