Best practice for shared child flows, especially when passing from dev to prod

[Anonymous]

Hi,

What is the best way to share child flows between solutions? Especially as it relates to exporting solutions from the dev to prod environment.

In my dev environment, I have a utility flow (U) and two flows that use it (A and B, in their respective solutions A and B). Should I create a specific solution for U and create flow U inside that solution? Or should I simply create flow U in the Default Solution?

I'm asking because when I try to export solutions A or B into prod, I oftentimes get some issues, especially regarding cross-solution dependencies and weird layering.

Thanks

[ArchitectMadhan]

Hi @Anonymous ,

Its better to have the Flow U in both solutions (Solution A and B), Solution A should contain both Flow A and U, likewise Flow B and U should be in Solution B. Because whenever you are exporting the solution A or B, always you get the updated Flow U.

[Anonymous]

Thanks @ArchitectMadhan for the response. However, I know U should be in A and B. I'm asking if U should be created in its own solution or if it should be created in the Default Solution.

[ArchitectMadhan]

Hi @Anonymous ,

Yes, you need to create U in its own solution, so that Flow U will be added to Dataverse and in other 2 Flows A and B It will be available under the section "From Dataverse".

[Anonymous]

I don't have an issue calling flow U from A or B, I am able to call that flow simply by using the Run child action, it is already showing up in the dropdown. I don't know why you're saying it needs to be available under "From Dataverse".

My issues arise when I try to export from dev to prod. I oftentimes get dependency complaints and if I do manage to successfully import a solution into prod, I see that my child flow (U) has layers mentioning multiple different solutions, which I believe should not be the case.

I'm wondering if, in dev, whether I create U in its own solution or whether I create it directly in the Default Solution may be a cause of these devops issues.

[Anonymous]

Perhaps this limitation answers my question?

 
"You must create the parent flow and all child flows directly in the same solution. If you import a flow into a solution, you will get unexpected results."

So does that mean that childs flows that are meant to be shared among different solutions cannot in fact be shared between those solutions? Doesn't that mean you have to make a copy of each child flow in every new solution where you are gonna to need it?

Also, does that not contradict this other statement:

"The flow is removed from the selected solution, but it remains in the environment. You can use the flow in other solutions in the environment at a later date."

And this one:

"Now you can build the parent flow in the same solution in which you created the child flow. Simply create a new flow. Alternatively, you can bring an existing flow into that solution."

???