In the December 2016 update for Dynamics 365 Business Process Flow entities were introduced. These entities are backing entities for Business Process Flows and are created when Business Process Flows(BPFs) are first activated. During this entity creation, a dependency is also created between a given BPF and its corresponding entity. This is to enforce that a BPF and its entity are always treated as a pair and there is never a scenario where a BPF can be introduced without its backing entity in to an org. that is on the December 2016 update for Dynamics 365 or above.
The following scenarios typically result in the failure called out above:
Scenario 1 – BPF in draft state
-
Navigate to Settings -> Processes
-
Create a BPF and save it. Do not activate it.
-
Add the BPF created in step 1 above to a solution and try and export it. Export will fail.
Scenario 2 – BPF activated from within solution explorer
-
Navigate to Settings -> Solutions
-
Create a new solution – SolutionA.
-
From within solution explorer for SolutionA created in step 2. above, create a new BPF from under the Processes node.
-
Once the BPF is finalized, activate it.
-
Click on ‘Export’ to export SolutionA.
-
Ignore the Missing Dependencies screen you are presented with that will call out the corresponding BPF entity that needs to be added to the solution.
-
Proceed to export SolutionA. Export will fail.