Flow goes lost while export/importing a solution between environments

[Vidhya1]

Hello all,

I have an app in Environment A that has a canvas app triggered flow. This app is available inside a solution as well. I m trying to export this solution and import it into Environment B. Everything in the solution gets imported successfully but the flow. The flow wont be connected when i try and look for it in the app's data sources.

Any guidance would be hugely appreciated.

Thanks

[UdayAdhikari]

Hi @Vidhya1 - did you add flow to the solution prior to exporting the solution? Both app and flow being called need to be in a solution before you export and when you import in a new environment both should come along fine however you still need to configure connectors(s), data source(s) used in the flow and activate it (it's off by default).

If you continue to experience issue, please document how you are creating your solution and send a screen capture of what you have in your source solution.

Thanks

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[Vidhya1 · Accepted solution]

I got it fixed... we wanted all of it work in our test environment without us editing the app or the flow... but we had no other option than that.... So this is what I did,

1. Export the app,entities and the flow as a managed solution
2. Import it into our test environment.
3. Open the flow in edit mode and re-assign the connections
4. Turn the flow on
5. Save the flow
6. Open the app and go to the flow trigger
7. Select triggering control -> property where trigger will be called in -> Action -> Power Automate
8. This will list out the flows available in the solution
9. Make a copy of the trigger from the formula bar (to retain the parameters and the return data)
10. Add the flow from the list and paste in the parameters and the formula that captures the return data
11. Save and Publish

But still we must be able to export and import solutions without any intervention. The connections has to be asked for, just like how it does when we export a flow/app package.

[TroyP]

Hi @Vidhya1 , can you provide screenshots for step 6 and above? I'm having the same issue and I'm not sure what I have to do for step 6 and above.

Thanks,

Troy

[Vidhya1]

Hello @TroyP, 

Were you able to locate your flow inside the app and was this flow created from PowerApps or was it created in Power Automate and included inside the app?

[TroyP]

Hi @Vidhya1 ,

If you're referring to the Flow banner/menu button on the top when the app is run, then this item is hidden. I hid this button so the users won't get curious and clicks around.

The flow was created inside the solution from DEV. Then the solution was exported(managed) from DEV as a zip file, then imported in UAT.

[Vidhya1]

Hello @TroyP ,

I had to edit the app in the destination environment and do those steps above. I understand that its in UAT environment. Unfortunately that's the only way I found that resolved the issue.

[nitintelstra]

We are facing the same issue. Even if you have connection references properly defined and environment variables to not change any thing in the flow in a managed solution. Still, we have to make the unmanaged changes to the power app to re-connect with the flows. 

Looks like a limitation at this moment. 

Nitin

[Anonymous]

We are facing the same issue. Hope Microsoft will provide an update soon

[elmz]

Hi Vidhya,

Do you have to reconnect all the connections if you have new changes to the canvas app?

Thanks!