cancel
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: Started
Comments
Advocate II
Advocate II

@R3dKap 

 

Thank you so much for that detailed explanation.

I was just going through everything and it seems like this doesn't work anymore. When importing the converted package, the to-be-created PowerApps Forms isn't visible. What is visible though, are the flows associated with the form. 

 

Could you confirm that or is it still working for you?

 

Thanks and cheers!

Super User

Hi @mrQ,

You mean that on the import screen, once the package has been uploaded, just before clicking the IMPORT button, you see only the flows but not the form ? Strange...

It's been a while I haven't done it though... I'll make a try on my side and provide you with the result...

Advocate II
Advocate II

@R3dKap 

 

That is exactly what I meant, yes.

I'll give it also another try and let you know in case its successful

 

I appreciate your community effort!!

Advocate II
Advocate II

@R3dKap 

 

I tried it again (...probably around 10-15 times) and I finally got it working. 

So it still works - all good!

 

@all others

Don't use PnP Provisioning Templates - they don't go well with the approach explained by @R3dKap. I ended up testing it several times until I finally found out its because of that.

Simply re-create the lists/columns manually or by script. Just don't use provisioning templates...

 

Cheers

Super User

Thanks for keeping us up-to-date... It's strange though that you can't make it work with PnP because I used it a lot to replicate my original lists and had no problem importing the forms following the procedure. I should probably give it a try nowadays. Maybe something's changed...

Advocate II
Advocate II

Oh okay... that'd be interesting to know whether this works for you or not. 

 

The problem I faced was that whenever I used provisioning templates, the formsettings.aspx page was still pointing to the SharePoint Form (default) and I couldn't change it to anything else. Neither was there a powerapps associated with the list or anything I could have deleted manually. I also tried to open powerapps, but because somehow pnp tried to import that as well, it failed and I wasn't even able to create new powerapps forms anymore. 

Regular Visitor

Hi @Jeff_Thorpe 

you have any idea when they are going to release this feature for package and deploy sharepoint customized form. Please update me if it is already released. Thank you.

Regular Visitor

Please NOTE:

 

Happy to see this started, however have just seen a behaviour you may want to be aware of. I have a client saving PWA sites as templates for re-instancing. We are working to add modern features to some of their lists including JSON view and column formatting and custom PA forms.

 

In our recent test to see if these components come across to the new site derived from the template:

 

  • The custom PA form does not appear to be present in the site copy instanced from the template, however clicking 'Customize with PowerApps' opens the customised form (!). Furthermore, the 'Back to SharePoint' link directs the user to the ORIGINAL site(!), not the copy we have just departed.
  • Also, PA data sources all still point to the original sources including the table source for SharePointIntegration. Not sure if I'm actually seeing the original form or a new copy of it. Looks like save/publish only affects the original and the reference to SharePoint list can't be changed.
  • View formatting survives, only column formatting that can be accessed via list settings screens survives.

Good luck.

Super User

That's interesting, thanks for sharing @goodspring...

Regular Visitor
@R3dKapYour instructions have worked perfectly upto today ;o( I now receive the following error message during a conversion: Enter the URL of the original (old) SharePoint site: [OLD_SITE_URL] WARNING: A newer version of PnP PowerShell is available: 3.23.2007.1. Consider upgrading. resourceMapping.csv generated Enter the URL of the destination SharePoint site: [NEW_SITE_URL] resourceMapping.csv fully complete Converting SiteUrl ...Done. ForEach-Object : The term 'resources[$i].newId' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\Development\Microsoft\FlowPowerAppsMigrator-master-mfa\ConvertPackage.ps1:20 char:14 + $files | ForEach-Object { + ~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (resources[$i].newId:String) [ForEach-Object], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.ForEachObjectCommand I'm using MFA, so to get to this point I had to add -UseWebLogin after the site URL in your PowerShell scripts. I'm not sure if this has a knock on effect or it's something else? I'm using the following versions: Microsoft.Online.SharePoint.PowerShell 16.0.9021.0 SharePointPnPPowerShellOnline 3.23.2007.1 SharePointPnPPowerShellOnline 3.12.1908.1 SharePointPnPPowerShellOnline 3.6.1902.2 Your help would be much appreciated.