I am attempting to create a Canvas PowerApp that exists within a Solution to a Flow which exists in the same Solution. I have been unsuccessful.
From the Solution-based PowerApp, I can select to create a new Flow, but after the Flow has been created, it exists outside of the Solution.
I can I create my Flow directly within the Solution and save it, and I can see it exists within the Solution:
My Flow is extremely simple, containing only a PowerApp trigger and a single Compose action (for testing).
However, from within my Solution-based PowerApp, the Solution-based Flow is not even visible to attach it:
Note that I can successfully attach a Solution-based PowerApp to a Flow that is not in a Solution, but the net result of this is that the PowerApp is packaged into the Solution, but not the Flow. The behaviour of packaging a PowerApp in a Solution differs from the behaviour when exporting a single PowerApp in isolation. When exporting a single PowerApp, when you import that PowerApp into a destination environment any Flows that are triggered directly by the PowerApp are embedded in the export file from the source environment and are deployed to the destination environment. When a Solution is packaged with a PowerApp inside of it, any Flows associated with that PowerApp are not embedded into the Solution. [Which is why I'm trying to include the Flow in the same Solution as the PowerApp].
Solved! Go to Solution.
Hi @aussiejedi ,
Thanks for feedback.
The issue could be reproduced by me.
From the Solution-based PowerApp, the Solution-based flow is not selectable.
I will help report this issue and back to you once I got any updates.
This is a feature we are urgently waiting on for automation of our deployment process.
Any chance we could recieve confirmation when this is fixed?
I would like to ask if there is any progress towards this topic. Maybe more accurate time since is already September. I'm about to start quite a complex project with powerapps canvas/flow technology at this is a very important topic for me due to lifecycle management and deployment to possibly multiple customers (tenants, environments).
Still really hoping this is coming in November as I've heard previously.
We've had to move onto model-driven apps in the mean time - we couldn't wait around for the deployment story with no clear timeline.
@SamWallis @nickdurak @v-yamao-msft
Any updates on this? I have a powerapp that is not part of the solution. I've created a powerapps trigger flow within the solution but when I click on Power Automate under Action, I couldn't see the solution-based flow I've created. Is this still a limitation? Please help.