web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Apps
Unanswered

Solution Exporting

(0) ShareShare
ReportReport
Posted on by 117

Hi,

 

I am having a really hard time trying to export a solution from dev to test environment...

 

I saw that Power Apps solution have some limitation regarding connection references and connectors, so I created 3 solutions:

 

  1. Application and Flows (contains 1 canvas app, 2 flows and 2 connection references)
  2. Tables (contains 3 dataverse tables)
  3. Connectors (contains 2 custom connectors)

Then I followed these steps:

 

  1. Firstly I successfuly exported the Connectors solution
  2. I tried exporting the Tables solution and I kept getting an error message saying that power apps could not find the tables in the test environment (but that is the reason I was exporting the tables solution)
    1. I had to export those tables manually
  3. I successfuly exported the Application and Flows solution

 

Now, when I try to execute the app on the Test Environment, nothing works and it is full of error messages.

 

What am I missing?

 

Thanks in advance!

I have the same question (0)
  • sudipm Profile Picture
    Microsoft Employee on at

    Hello,
    I am not 100% sure on what you meant by certain things like, "had to export tables manually" and also why there was a need to create 3 separate solutions.
    However I will try my best to take a stab at this.

    Firstly dont create 3 separate solutions, Create 1 single solution on your dev environment containing all the tables, connectors, conn references etc. Use the Maker portal and not the old portal to create this solution, there is no known limitations on the maker portal for the stuff you listed above, and if you can do it in 3 solutions it will definitely work in a single solution also.

    Ensure in the solution you have added the site map and and the app also. This is not always obvious, but if this is a new app its always good to do this.

    Export it as a unmanaged solution, it will make your life easier while you figure things out, you can later export as managed if that is something that is needed.

    On your higher environment if you created tables, fields manually with same name earlier, please delete them, the solution above will recreate them (this will result in data loss, so do this only if this is not production or data is not important right now)

    Try to import the unmanaged solution via the maker portal to your higher environment. If all components and dependencies are correctly added, it will go through, else it should tell you what is missing, add those to the same solution on the dev environment and re-export. Repeat this till no dependencies are being flagged while importing the solution to your higher environment. 

    It should work, if this helped you solve the issue, kindly mark as the solution.

    Thanks

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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 505

#2
WarrenBelz Profile Picture

WarrenBelz 502 Most Valuable Professional

#3
Haque Profile Picture

Haque 324

Last 30 days Overall leaderboard