Answered

Export Issues

(0) Share

Report

Posted on by Ferminaterz

150

I am trying to export a Power App out of one environment to another, but it is not showing my flows associated with the app, picture below. I even tried importing back in a previous version but get the same error. It only happens for one application and in one environment. There is an error icon, but it doesn't open. If anyone has any clues let me know because I am stumped.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (2)

Sort by

Suggested answer

SebS 4,822 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

The app must be exported as part of a solution with all flows, connection references, and connections included If you want to have all import to new environment

Was this reply helpful? Yes No
Ferminaterz 150 on at

Like (0)

Report
Copy link

Link copied!

The items have never been in a solution before. yes, I know it is best practice but was affecting my flows, so I just did a straight import. This app has been updated several times over the last three years and just seeing this problem now.

Was this reply helpful? Yes No
Verified answer

Ferminaterz 150 on at

Like (0)

Report
Copy link

Link copied!

The solution that I found was to refresh all the Automate connections from within the application. Why it works not sure but will look into it more.

Was this reply helpful? Yes No
Verified answer

SebS 4,822 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

It’s much easier to manage apps and flows when they’re built and deployed within a Solution.

The issue you’re experiencing is due to the lack of a Connection Reference, which is required to maintain solution integrity when flows are used.

A Connection Reference defines how your flows connect to data sources (like SharePoint or Outlook) and ensures the link between the app and flows remains intact across environments. Without it, flows lose their association with the app during export/import, which is why they’re not showing up.

To fix this:
Move all your flows into the same Solution as the app.
Create and assign a Connection Reference for each connector your flows use.
Re-export and import the entire solution — this will keep the app and flows properly linked.

If connection references were not configured originally, you’ll need to move and reconnect the flows manually in the new environment. The same approach applies to component libraries — they should also be part of the Solution to preserve dependencies.

If Solution Container fix will not be an option for you try manualy move All flows to target Enviropment

1 people found this reply helpful.

Was this reply helpful? Yes No
Ferminaterz 150 on at

Like (1)

Report
Copy link

Link copied!

Thanks for the @SebS. The few times that I have used solutions; a flow might work for some but not others. Then since I created it, it would always work for me so couldn't replicate to troubleshoot. That is why I make them standalone and just import and export with the app. In the three years I have been working with Power Apps that is the first time seeing that. I will start with one of the smaller apps and put them in a solution.

Was this reply helpful? Yes No