Answered

Transfer power apps from Dev to Prod use solution and environment variable

(0) Share

Report

Posted on by railgun0w0

Hi everyone,

Hope you're all doing well. I have a somewhat unusual question regarding transferring my Power Apps solution from the development environment to the production environment.

I've set up two SharePoint lists, one for development and one for production, and I've copied the list from development to production.

However, during the solution transfer, even after updating the environment variable to the new SharePoint link, the app in the production environment isn't functioning as expected. I tried transferring it as an unmanaged solution and, after editing the app and encountering some initial errors, it worked fine upon saving and reloading.

Is this a typical method for transferring solutions between different SharePoint sites?

Are there any strategies to avoid these issues, as the ALM is more like a managed solution in the production environment?

Thanks for your insights!

Categories:

Building Power Apps

All responses (2)

Answers (1)

Sort by

Verified answer

BhargavPatel 660 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@railgun0w0 Ideally you will go from Dev to Test, and everything checks out in Test, only then move the solution from Dev to Production.
Avoid moving unmanaged solution to production and changing anything in production because you won’t be able to remove the changes to unmanaged layer if you try to overwrite it with managed layer later on. Depending on the complexity of your solution it can get messy really quick. Then to resolve all such issues you will have to start from scratch by removing every object of the solution from the environment.
So, keep unmanaged solution in Dev, move it as only managed to Test, and if everything looks good move it as managed to Production.
railgun0w0 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you so much.
I find that my Sharepoint List I connect does not use the environment variable.