Showing results for 
Search instead for 
Did you mean: 
Advocate I
Advocate I

Deploying Canvas App with Flows

Hi folks,


do you have any advice on deploying flows implemented in canvas apps to managed environments?


We have the following scenario:

- target environments are managed, so creating active layers by doing customizing on the targets is no option
- We have a canvas app which has several flows implemented
- Flows can be added to solutions in general, but flows with a manual trigger or canvas app trigger (which we need, since we want to trigger the flow from canvas app) cannot be added to them (only God know why 🤔), so we need to deploy each Flow manually to every environment


This results in having the wrong GUIDs of Flows assigned in the canvas app (since Flows will get a different GUID when deploying them via Flow export/import) on the target environment and we need to adjust the assignment manually...

Is there someone with any hint or advice on this or at least facing the same issue? 


Community Support
Community Support

Hi @HerrMueller ,


Why not update the solution from the beginning?


Add the flow into the solution and edit the App to trigger the flow with a button, export as a managed solution, and at last update solutions that in all the other environments.


Hope this helps.


Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Super User
Super User

Make sure you're only using Flows that were created from a Solution, not ones that were created from someone's personal MyFlows then added to the solution.

The reason is the distinction between Connections and Connection References. When you create a Flow from MyFlows, by default it uses Connections, which are static references to a set of values (the dataverse db, for example) but when you move that in a solution, it doesn't update, so it breaks.

On the other hand, Connection References are the default when you create Flows directly from a Solution and during Solution Import (if using the modern UI) the interface will prompt you to redirect these references to whatever the relevant connection information is in this environment (i.e. the relevant Dataverse db here).

Hi, we did this, but does not work as expected, we raised a support case for this. (2109150050000130)

Helpful resources

Microsoft 365 Conference – December 6-8, 2022

Microsoft 365 Conference – December 6-8, 2022

Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.

Users online (5,103)