Bug? Add-PnPContentTypesFromContentTypeHub doesn't work in Private or Shared Channel Sites #1770
Unanswered
sparkitect
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This command fails if the Content Type includes a Managed Metadata column AND the site is a Channel site (Private or Shared):
I believe this is because the activation of the hidden "TaxonomyFieldAdded" Feature has been skipped in the interest of fast creation of the site.
The work-around is to run the following command prior to this one:
Enable-PnPFeature -Identity 73ef14b1-13a9-416b-a9b5-ececa2b0604c -Scope Site -Force
I believe this to be a bug that exists at a lower level than PnP, so changing the Add-PnPContentTypesFromContentTypeHub command so that it activates the Feature for us seems silly.
Here's a screencast of me speedrunning the bug and work-around: https://youtu.be/_Ty_hXOGhOY
Beta Was this translation helpful? Give feedback.
All reactions