msft-github-bot
commented
5 years ago Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
Open rmunasinghe opened 5 years ago
msft-github-bot
commented
5 years ago Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
NicolajHedeager
commented
5 years ago We started to see this error around the 7th of August as well.
The SharePoint Server-side APIs throws a NullReferenceException when we try to update the title of a list. This is done in plain CSOM, without the PnP provisioning engine. If we try to change the title in the browser, SharePoint also shows an error page.
We found that this was only happening on lists which had an invalid Managed Metadata field i.e. the termset for the field had been deleted in the taxonomy store. Deleting the invalid Managed Metadata field from the list solved the issue.
andrewconnell
commented
5 years ago This should be posted to the relevant PnP project, not the general sp-dev-docs issue list that's meant for SharePoint development questions. Moving this issue to the relevant repo...
ghost
commented
5 years ago Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
AndyBolam
commented
4 years ago I think I'm seeing this in some PnP templates that we are running under an Azure function (V1), but I need to understand if this is my error or this bug :) Seems it hasn't been looked at for a while.
towerbe
commented
4 years ago Wondering if anyone has made any progress on this issue?
I am trying to use Apply-PnPProvisioningTemplate to "copy" a list from one site to another (just the structure). I am using the appropriate parameters to limit the handlers to Lists. The list actually gets created, but none of the columns get created. The cmdlet fails with the same error as specified in this issue title. That's the only error I get.
Any help is greatly appreciated.
SharePoint/sp-dev-docs#3956 ## Category
Expected or Desired Behavior
PnP Template applied to site without errors.
Observed Behavior
We have several different instances of site provisioning PowerShell scripts that have suddenly stopped working despite not making any changes to them in a while. It appears to have occurred sometime after August 7, 2019.
Output from PnP Trace Log:
Steps to Reproduce
I can provide the PnP template .xml file if required. The above site has two custom content types and adds those content types to the default "Documents" library.