Move SharePoint List Forms to a different environment

[sharepointguy]

By default, all SharePoint List forms that are modified in PowerApps are created as apps in default environment. However, my form uses a few differnet connections to multiple data sources which I would like to secure so that not all users can use that connection. Is there a way I can move the forms to a differnet environment from default?

[PowerAnalytics · Accepted solution]

Hi @sharepointguy,

do you want to change the environment of your custom SharePoint form?

Unfortunately this is not working.

See the Q&A:

Q:Can I customize a form in an environment other than the default environment in my organization?

A:No. 

https://docs.microsoft.com/de-de/powerapps/maker/canvas-apps/customize-list-form 

[sharepointguy]

Hi @PowerAnalytics ,

Thanks for your response.

[KoenReynaert]

I just read the following: "...In addition to the ability to save SharePoint custom form resources to a non-default environment, it is also possible to limit maker privileges to only be able to create and edit SharePoint custom forms in a non-default environment." 

... in this article:
Manage Power Apps - Power Platform | Microsoft Docs

No more info on how this is done practically

[Anonymous]

HI KoenReynaert,

Thanks for that article.

The article does detail how to set the 'SP custom forms' envirinment. It does explain, that exisiting ones cannot be moved, but only new ones wilbe placed there.

It is changed using PS

Set-AdminPowerAppSharepointFormEnvironment –EnvironmentName 'EnvironmentName'

[Anonymous]

Will Set-AdminPowerAppSharepointFormEnvironment –EnvironmentName 'EnvironmentName' change where I integrate list forms with Power Apps? Microsoft doesn't explicitly mention list forms for that cmdlet. Also, if it does set a new environment for list forms, does that mean existing customised forms in the default environment get reset to non-customised / default SharePoint list forms?

[UnsuckM365]

This is an old thread, but it seems not much development has happened on this over the years. Has anyone actually tried this solution and what lessons have you learned? The documentation is still so sparse...

[pnthrzrule]

Yes, I have some brand new experience with at least creating a new environment for new customized list forms. Here are my findings and I hope this helps save someone about an entire days work that it costed me to figure it all out...here goes:

• Scroll to the bottom of this page (https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/customize-list-form) and you will find a link to a white paper detailing how to create a new prod environment for your future SharePoint customized list forms (it also shows how to move existing forms to the newly created environment, which I haven't tried yet)
  • Please note there is a typo in the powershell command!
    • There should only be a SINGLE dash in front of the Environment name portion as seen in the threads above. The pdf white paper shows 2 dashes
    • If you use 2 dashes you are going to get a stupid dumb error that has nothing to do with the fact that you used too many dashes
• After you create the new prod environment and run the CORRECT command with no typos, you will find that you can customize the form just fine, save just fine, and publish just fine in the new environment
• However, when you go back to SharePoint and click "New" you may find that your customized list form does not launch
  • Instead you see the same old default SharePoint list form
• If the new form fails to launch, go back into editing the customized form and adjust the settings to use "Modern Controls and Themes" as seen in the screen shot below

• Republish and try again....your customized form should launch
  • It may take several browser refreshes
  • I have no idea why this is the case
  • If you don't want to leave the modern controls turned on, you can turn it back off and publish and the form should continue to work

Please let us know if any of the above helped! Good luck!

[ecflyer]

Thank you for your post. I have managed to create the new environment and set is as the default environment for new custom forms. Next step is going to be moving an existing form to the new environment. I don't normally like using integrated forms, but at least now it will be more secure.