Showing results for 
Search instead for 
Did you mean: 

Move or Copy a SharePoint list PowerApps Custom Form

It would be nice to be able to create a SharePoint list PowerApps Custom Form in one site or list (e.g. development) and then be able to move it to another site or list (e,g, production). This would help with development and teting of new and updated forms before they are released to the production. This could also help with the reuse of form designs, so a person isn't always recreating the wheel.

Status: Under Review
New Member

11 pages and no solution, very predictable.

Regular Visitor

Hi @CTrudgeon , apologies for the late response. I had some issues with the migrator and I just haven't found time to troubleshoot. For example when I selected migrate my tables, it didn't work properly some tables were done some were not. To be fair I need to allocate some focus on it as it is very critical that I get this pinned down.

Kudo Kingpin

@BhutiM I am interested in fixing all issues related to the Flow & Apps migrator. If it's not too time consuming, would you be able to submit a short description of the issue you were having?

Power Apps

@Jeff_Thorpe   If you want to move the SharePoint list itself to a production environment, then can't you use these move steps?  If you want to leave the original in place, copy it to a prod site and then use the original as a dev environment, can't you use these copy steps?   And, then use environment variables to move your Power App from dev to test as you change it?   SharePoint is actually the only data source we currently support for this scenario (more coming soon.)  But, doesn't that satisfy this scenario?

Regular Visitor

Hi Guys


I actually forgot to share my workaround this issue. I created a field called Environment in my main lists and made it a choice of Prod, Dev and Uat. In PowerApps I then have a variable that set the default environment depending where the app is. In that way I don't have to change anything when my app goes to uat, or prod. 

Also ensuring my workflows are attached to my PowerApps makes it easy to deploy the application.


The main step is that as soon as my app is in production, I edit it and change my variable to Prod and publish and all users will see only Prod data in my app but the ones on Dev will only see Dev.


I hope that helps.





Memorable Member

@BhutiM That was a really good workaround, thank you

Kudo Kingpin

How about embedded Power Apps (forms) associated with a SharePoint List to allow ALM between dev, test, and prod instances of SharePoint lists that have embedded Power Apps? 


I guess the real question - Can embedded apps (forms) be packaged up (imported) into a solution to take advantage of Environment Variables? If so - how?




Kudo Kingpin

Update to using Environment Variables with Embedded Apps - I did a lot of research and I don't see a way to do it.  I tried creating a solution then importing it but could not replace the existing connections that I had already created in the embedded app (App associated with a SharePoint List item when you replace existing form with a Power App). 


I also tried creating a new stand-alone app and then deploying it as another version within the same environment - the idea being you would have dev, prod, test in the same default environment you get with O365 since we are using SharePoint as the data Source rather than Dataverse - we don't need any instance of Dataverse - and that is a No Go - you can't  do it - you must deploy the solution into a different environment and to make an environment I believe you need the paid version of Power Apps.


Now the good news - our company has a tool that will let you move embedded Power Apps or stand-alone apps and you can deploy multiple versions of that app in the same environment as long as you give them a different name - all in the default environment you get with O365.


You can take a look at how it works by watching the video's at this link

P2P Express - ALM for SharePoint based Embedded Apps  


If you are thinking about building a reusable solution based on SharePoint to sell or for internal use, we can customize our tool (P2P Express) so it is 1-click deployment (more or less)  if you want to make an app that you resell and want to deploy into a customers environment.


I was hoping environment variables would do the trick for moving embedded apps and deploying multiple versions of the app within a single environment given we are not using Dataverse but it looks like our tool is the way to go. 


I know most of our customers are using embedded SharePoint list apps since their user base is familiar with the SharePoint List UI and like the capabilities to create custom views and filter/sort/search using the native SharePoint list capabilities


Check  out our tool - P2P Express - and please chime in if you have any info on how to use Environment Variables with embedded Power Apps associated with a SharePoint list to support ALM or how to deploy multiple versions of a solution within a single environment using Environment Variables

Regular Visitor

Hi @skylitedave 


Yes the environment variables are limited to Premium and using Dataverse so SharePoint solutions are not covered. I also like the packaging the solution part of PowerPlatform if only it was covering SharePoint as well not only DataVerse.


Your idea of deploying the app in the same environment would be a mess for the organization I work for, hence I decided to have UAT, DeV & Prod. In the same environment when you have lots of powerApps and PowerAutomate it becomes a daunting task. We also like to use Monitor Cloud Flow Activity so I would like to have a seperate enviornment to be able to pick issues that need addressing faster rather than going through the thousands of flows in the same environment including Dev flows.


That's my opinion. So far the idea of having a field in my tables that seperate dev/uat/prod has worked better for me. Even when I buld PowerBI Reports I use those variables to pull out the correct data.





Kudo Kingpin

Hi BhutiM,


We handle the "mess" you reference through permissions (who can access the app) and naming conventions but understand your opinion.


Couple of follow-ups

1 - Do users need a premium license to access apps in environments beyond the default environment?

2 - Can you explain a bit more on how you use a field to handle multiple versions of your app through environment variables?

3 - I don't see any way to access/use Environment Variables with embedded Power Apps associated with a SharePoint list. Do you know of a way to do this?


Thx for helping all of us wade through this!