Invalid field name "TaxCatchAll" on Apply-PnPProvisioningTemplate

BraunJonathan commented 5 years ago

Reporting an Issue or Missing Feature

Expected behavior

The PnP template gets applied to a Communication site on running the Apply-PnPProvisioningTemplate command

Actual behavior

Exception Message: Invalid field name. {f3b0adf9-c1a2-4b02-920d-943fba4b3611} occurs nearly all the time on our production tenant. For us, it is a blocking problem in production as we developed an on-demand process to allow users to create templated sites. For a few weeks now, this does not work anymore due to the given exception...

Steps to reproduce behavior

The problem is decribed in full in issue #1180 but the author does not seem to want to reopen the issue despite several people having the problem.

When applying a template whith a content Type using taxonomy based metadata, it crash every time with an Exception Message: Invalid field name. {f3b0adf9-c1a2-4b02-920d-943fba4b3611}

We wait 15 minutes after site creation before applying the template.

Which version of the PnP-PowerShell Cmdlets are you using?

[X] PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?

(you can retrieve this by executing Get-Module -Name *pnppowershell* -ListAvailable)

How did you install the PnP-PowerShell Cmdlets?

[X] Installed through the PowerShell Gallery with Install-Module

ghost commented 5 years ago

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

andygjones-nz commented 4 years ago

We're experiencing the same issue intermittently in production. Sometimes it's fine immediately after group/site creation, other times it can take an hour or more before this error resolves. It's really making automated provisioning a struggle.

mag210 commented 4 years ago

Exactly the same for us. This is basically a blocking issue if you are trying to do anything more than the most straightforward of site provisions. Are there any suggestions on how to resolve?

guillaume-kizilian commented 4 years ago

@mag210 For us removing those two lines from our content type provisioning did the trick :

            <pnp:FieldRef ID="f3b0adf9-c1a2-4b02-920d-943fba4b3611" Name="TaxCatchAll" Hidden="true" />
            <pnp:FieldRef ID="8f6b6dd8-9357-4019-8172-966fcd502ed2" Name="TaxCatchAllLabel" Hidden="true" />

pnp / PnP-PowerShell