Import managed solution with BPF prefix new_

There are some issues when you upgrade the Dev environment and you have custom Business Process Flows (BPF) and when you export the solution with that BPF as manage and import in the Test/Prod environment but it is giving an error. This is because the prefix of the BPF is with “new_” instead of the prefix of the solution.

 
There is a known article that explains how to solve the issue:

https://support.microsoft.com/en-us/help/4020021/after-updating-to-dynamics-365-mismatched-business-process-flow-entity

Following the steps will help you to overcome this issue without having to open a support ticket or running scripts directly in the DB.

Have in mind that these steps are to be performed in the sandbox that there isn’t any problem deleting the BPF so the records related to that are all deleted.

Hope this helps.

Advertisements

Business flows not switching by Workflow/Plugin

The problem is when you want to have a Business Process Flow (BPF) that changes automatically when a user changes a field, but that process flow is only changing to that user and not to the others.

For example:

When user1 changes the field, he can see the BPF changing after the reload of the form. When user2 looks at the same record, he can’t see the BPF changed.

This happens because the BPF’s in Dynamics 365  allows multiple processes to run concurrently against the same record and the process that is running for a user might not be the same to the other user.

To have a workaround that works, it is necessary to implement a JScript OnLoad calling that will set the active process in the record to the one that the user wants, for that it can be used Xrm.Page.data.process.setActiveProcess/setActiveProcessInstance.

If you want to know more about the new BPF and how it works, take a look at this post.

Hope this helps.