Announcements
I am trying to import a solution from one environment into another. It's a test solution containing a CanvasApp and an Instant Flow. The CanvasApp simply has a button which triggers the Instant Flow via a Powerapps (V2) trigger. I have noticed that when I import the app into the new environment, that the imported PowerApp is not connected to the imported flow. Instead it still references the flow id from the previous environment. To fix this, I am forced to delete the flow connection in the app and reconnect to the new flow. I have seen other posts suggesting that this should work @Jcook (https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-reconnect-flows-in-a-canvas-app-after-import/td-p/946623), but certainly is not working for me. The PowerApp was created from within a solution, and the flow itself was created from within the PowerApp.
Hi @MJKirts :
I've made a test but did not encountered the problem you mentioned.
Please check if you have theses permissions:
Best Regards,
Bof
Hi. The application user that imported the solution has System Admin security role. I assume it would have such permissions? Can you provide exactly the steps you performed here so I can compare?
Anyone who uses this app must have these two permissions.
The issue I'm having isn't with being able to run the flow after it has been imported. The link to the flow is actually wrong after the solution has been imported to another environment. If I export a solution from a Dev environment, then import it into a Test environment, the URL for the flow in the Test environment is still pointing to the Dev environment. I then have to delete that link, and link it to the correct flow to make it work. See below..
After import I go to my PowerApp and press Edit on the Flow that is connected to the PowerApp
Then I get this error. The Flow ID it is referencing is the Flow ID from the previous environment.
"Error: Could not find flow '42c2d3fc-5809-4db4-a678-2586912c1111'"
I can confirm that the user has all of those required permissions as they are a System Admin and the System Admin security role has those permissions.
Can you document the steps you followed please so I can try to reproduce on my end please?
Hello @MJKirts
I believe you should try and create the Flow inside the solution and than add the Power Apps trigger V2 with parameters and link the app and Flow.
@MJKirts @v-bofeng-msft @Jcook Am also facing same issue. I have all the security permissions. But still the connection references of power automate is broken in power apps after solution import into test environment.Can you please let me know if you already have any solution for this.
@vamshi I never found a solution, but what I did realise is that despite the link to the flow being broken when you press edit, the app does actually run correctly and call the correct flow when published. So it seems to just be a problem with the editor that does not actually affect running the application. We could live with that because we won't allow editing of the app in a production env anyway.
@MJKirts@v-bofeng-msft @Jcook In my scenario, am using managed solution to import in new environment and when we try to play the app it is throwing error "connection not configured for this service". Am using instance flows with the power apps V2 trigger.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 541
WarrenBelz 434 Most Valuable Professional
Valantis 289
