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.
