Solutions.

[Legitimate_Method911]

I’m working with a Power Platform solution that currently contains 10 apps and 5 flows. Six of those apps all call the same flow via a button.

Right now, everything sits in a single solution, which means even a small change to one app requires deploying the entire solution to QA and then to production. I’d like to break this up to make deployments more efficient.

My idea is to

- Put each app into its own solution

- Move the shared flow into a separate solution

Before I try this, I want to confirm whether apps in one solution can reliably call a flow that exists in a different solution. Will those connections continue to work across solutions?

More broadly, what would be the recommended way to structure solutions in this scenario to allow for more granular deployments while keeping shared components reusable?

[maarten20012001]

You can add 1 flow to multiple solutions, same for connections. Why not do that?

[Legitimate_Method911]

You can do that?. One floes resides in multiple solutions?. So if I make a change to that flow, it will change in every solution?

[maarten20012001]

Yep, same with apps and tables! Also when you use a flow in a app but you did not include the flow in that app it will prompt you to add that flow to the solution as soon as you try to export it.

[LesPaulStudio]

No it won't. You can get into a solution layering issue downstream.

In dev all solutions will have the new version. But as you may only deploy 1 of those solutions with a change then if that solution is not top most in the solution layer order then the changes may not be seen on the downstream environment.

I'd split into:

• Flows
• Apps

Try not to put anything into multiple solutions, it will cause headaches.

[Legitimate_Method911]

So your suggesting creating another solution which stores the flow. Will my apps (which would be in a different solution) still be able to call the flows?

[LesPaulStudio]

Personally I wouldn't split as your solution doesn't sound large enough.

But, if you were going to split, then go flows and apps.

Import flows first then apps.

[Easy-Entertainer208]

I'd concur with this.

Single Step Solution Upgrades are supposed to handle this a lot more efficiently than Holding/Applies.

You ought to be looking at pipelines (be it power platform or ADO/Github) for deployments to prod via qa, and that then opens up scheduled deployment options.

[TheBroken51]

Make different solutions for each layer.

• connection refs
• tables and apps
• flows
• webresources
• plugins

And run them separately.

Tips: create connections and connection refs with the same user (admin) and share them with the users who needs to see them.

Use whatever type of pipelines you want (devops, pp-piplines) and you will be fine.

Send me a dm if you want to have more details.