Contradictory statements in Power Automate docs?

Question

Note: this is a Power Automate question but it won't let me tag it as such

Hello,

I've posted this question in a number of different ways on the forums without any luck. This is regarding where (ie. in what solution) to create child flows that are shared between different solutions.

For example, I have two flows A and B in their respective solutions A and B, which both call a child flow U. I have created flow U in solution U. However, due to some layering issues in our production environment, I'm wondering if I should have just created flow U in the Default Solution instead of its own solution U. In order to answer this, I did some research, which brought up some seemingly contradictory statements.

• "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. (source)"

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?

And does that not contradict the following two statements?

• "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. (source)"
• "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. (source)"

Answer 1

Power automate is not currently supported here on Q&A. The product group for Power automate actively monitors questions in dedicated forums here.
https://powerusers.microsoft.com/t5/Microsoft-Power-Automate/ct-p/MPACommunity

--please don't forget to upvote and Accept as answer if the reply is helpful--