pnp / PnP-Sites-Core

Microsoft 365 Dev PnP Core component (.NET) targeted for increasing developer productivity with CSOM based solutions.
Other
415 stars 642 forks source link

Apply-PnPProvisioningTemplate when there was a customized list form prevents new list from using PowerApps form #2635

Open Lucho1970 opened 4 years ago

Lucho1970 commented 4 years ago

Category

[X ] Bug [ ] Enhancement

Environment

[X] Office 365 / SharePoint Online [ ] SharePoint 2016 [ ] SharePoint 2013

Expected or Desired Behavior

When using the Get-PnPProvisioningTemplate to export a list where the view was customized using PowerApp, I would like that PowerApp to carry to the new environment which in my case would be a new Tenant as I have done my development on a Dev tenant.

Observed Behavior

When the list is created, everything seems fine except the list is using the OOTB SharePoint form. When I try to Customize with PowerApps, I get an "Error opening file" message with the application id of the original form. There is no option but to close this. And I cannot modify the form.

Steps to Reproduce

From a list in one tenant, Customize the form using PowerApps. Export the template using Get-PnPProvisioningTemplate -Out ".\SampleTemplate.xml" -Handlers Lists

From a different tenant, Import the template using Apply-PnPProvisioningTemplate -Path ".\SampleTemplate.xml"

Go to the list and try to customize the form.

ghost commented 4 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.