Unanswered

Adding flows and apps into a solution

(0) Share

Report

Posted on by FV-31101624-0

When adding an existing flow and app into a solution, it seems to create a link between the apps and flows, rather than copying the app and flows into a solution.

The issue with this is that when you e.g. delete a flow under My Flows, and attempt to update the flow in the solution, you get a 404 error as the flow can no longer be found. I tested this by creating a very simple flow, adding this to a solution, publishing the solution and subsequently deleting the flow under My Flows.

Is there a way to copy flows and apps into a solution so there is e.g. no longer a link between the flow in "My Flows" and the solution, or is there a step that might have been missed?

I know it is possible to

import/export solutions, but I don't know if this retains the link to the original flow - the ownership might change of the solution, but it is unclear
export flows and apps, but I can't find a way to import exported flows and apps into a solution (no Import option, just create new or add existing with a link to an existing flow inside or outside the dataverse)

Key concerns are that a solution might break or needs to be rebuilt if an owner creating a solution or linking a flow/app into a solution an subsequently delete their "own" copy or someone leaves the organisation and their account is inactive/removed, the solution can no longer be maintained and flows/apps might need to be recreated.

There also doesn't seem to be a way to roll back a solution if it is broken where a copy of a flow or app is restored, so the only option seems to be to share an app with other several individuals to retain business continuity (which I would've hopes the Solution ALM capability would address alongside version control).

Any advice appreciated as we're looking for a viable ALM solution for apps and flows without having to export apps/flows and store copies of flows and apps in a repository outside the solution.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Mark Nanneman 991 Super User 2025 Season 2 on at

Like (0)

Report

When you add an existing object from your Environment to a Solution you're basically creating a 1:N relationship. An object (Table, App, Flow, Choice Set, Plugin, Web Resource, etc) can be in multiple (N) Solutions, but it can only be in the same Solution once. It's something like a user being in multiple Teams.

If a Solution is broken, or needs to be rebuilt, you can import an earlier exported copy of that solution. For example, if you put a flow into a Solution, export the Solution, then delete the Flow, you could just reimport the last Solution export and it will create a new copy of your flow. The same is true if you say, delete a column or a view on a table--you can get it back by just importing the solution again.

Keep in mind, if you export a solution as "Managed" then the flows in it can't be deleted once it's been imported to a new environment.
The idea is you have an environment where you build your solutions, test them, then import them as managed solutions in the production environment.

I'd recommend creating a development environment if you don't already have one, and experiment with creating, exporting and importing solutions there.
I'd also recommend reading more on Solutions from learn.microsoft

https://learn.microsoft.com/en-us/power-automate/remove-solution-aware-flow

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solutions-overview

https://learn.microsoft.com/en-us/training/modules/introduction-solutions/

Was this reply helpful? Yes No
Suggested answer

FV-31101624-0 4 on at

Like (0)

Report

Thanks for the response.

I will take this into consideration for a proposed process. My main concern is that people might delete the source app in their own environment after adding it to a solution as the though process might be that if it is added to a solution, it is no longer needed in a personal environment or if the original implementer left an organisation that the flow is no longer accessible to edit for whatever reason.

While I understand it is possible to import a solution, it does not appear to be possible to import an app or flow into a solution (you either link it or create it in a solution). Again - something to consider for a policy/best practice to mitigate BCDR risk.

It might be something as simple as (on the top of my head):

- Always ensure an app/flow has a shared owner with someone once productionised (e.g. a contractor has to share it with one or more permanent employees in a company so access is retained)

- Always ensure the app or flow are part of a Solution once productionised

- If in doubt, (re)build the app/flow inside a solution rather than a personal environment and link it in a solution.

- Ensure implementation documentation is in place so it can be rebuilt

- Ensure the solution is version controlled in a separate repo (like Github or similar)

Was this reply helpful? Yes No