Is it supported to package a canvas app and a flow in a solution where the flow is called from the that canvas app. With some recent changes I am now able to create a package that has both the canvas app and the flow in it. Now I am able to configure the canvas app to call the flow, but I encounter a problem when I export the solution and import the solution back into another environment. The connection between the canvas app and flow is removed. Under the connections pane it shows the flow as “Not connected”.
Before pursuing this approach further is this scenario supported?
Solved! Go to Solution.
The above image is from Limitations of Solutions
From point 1, it states, it is possible to create a Canvas app button triggered flow from Solution which means the flow can be packaged in a solution. So now the solution is exported (unmanaged) and imported in new environment.
From point 2, the behavior is expected that connections will break. But when i try to edit the button inside the app, i do not see the flow which is inside the solution. (I have turned On the flow too). How to handle this scenario? I am planning for CI/CD and hence want to avoid exporting/ importing each flow separately.
From point 3 is an expected behavior but it becomes difficult to find the list of all flows inside the environment.
Any suggestion or recommendation on how to fix or handle the above scenarios.
If importing the solution results in the canvas app dropping the link to the flow, what the heck is the point?
I have complex flows called from a canvas app. I have dependencies on custom CDS entities, and would like to use child flows, both requiring a solution. But.. I can't use a solution cause it breaks the link between my canvas and flows?
These limitations are ridiculous and really undermine the utility of the framework for anything other than personal use. The ability to develop a solution for someone else's environment is wrought with gotchas and pitfalls.
The limitation is bit frustrating if we have lot many connections.
The easiest way to fix this is add a dummy screen in your app and just create a new data/ flow connection. This will save you from overriding the complex formula which is written for invoking a flow while restoring the connection the flow.
Application Lifecycle Management through solutions in the Power Platform...
Only Production Ready for Data Model and Model Driven Apps from my experience... wonder how Dynamics Companies have been using this for years??
Environment Variables --> bugs
Power Automate Flows on entities from Model Driven App --> workaround needed outside solution
Power Automate Flows in Business Process Flows of Model Driven --> not working in most browsers
Power Automate Flows linked to Canvas Apps --> reconnect of App to Flow needed after Export/Import
and this is just after half a day of testing...
Still: I have faith 💪
I am having very similar issues
I have a Power Apps Solution that contains a Model Driven App(MDA), Canvas App and a Power Automate Flow.
The MDA has a page which contains a Canavas App. This Canvas app asks the user for some data input. Then the user click a button on the Canvas App to trigger a PowerApp flow which uses the user data input to drive the flow.
Everytime I import a new solution from the Dev environmante into this Sandbox Environment I basically have to rebuild sone of the Flow actions and reconnect it back to the Canvas App.
This is very time consuming.
If anyone has ideas to help improve I would love to hear them
Check out our new profile badges recognizing authored solutions!
We are excited to announce the Power Apps Super Users!
Did you miss the call? Check out the Power Apps Community Call here.
Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!