Replies: 2 comments 1 reply
-
|
I just found a quick fix. Add a sitecolumn to the site with the same name as missing. Then try to add the Add-PnPContentTypesFromContentTypeHub again. You then get an error stating that there is conflicten sitecolumn. Then you remove the sitecolumn again and then when using Add-PnPContentTypesFromContentTypeHub again the missing column is also available :-) |
Beta Was this translation helpful? Give feedback.
-
|
hi @Wernbe , looking at your workaround, the problem seems to be coming from the server side and not the cmdlet itself. Would recommend reaching out to Microsoft support for help, we can't do much here, so will move it to discussions. You can ask them to look at the cmdlet code here: |
Beta Was this translation helpful? Give feedback.
-
|
@gautamdsheth Thanks Gautam, We will if the problem arises again. |
Beta Was this translation helpful? Give feedback.
-
Reporting an Issue or Missing Feature
In some cases when creating a team and when using Add-PnPContentTypesFromContentTypeHub -ContentTypes to add an contenttype to the sharepoint site->list. One of the columns of the contenttype is missing
Expected behavior
In most of the cases the contenttype from the hub has all the columns.
Actual behavior
One of the columns is missing.
Steps to reproduce behavior
Add-PnPContentTypesFromContentTypeHub -ContentTypes "0x01006E4EB9BA6BA49944B4D15C7BC50B646D"
What is the version of the Cmdlet module you are running?
Running 2.1.1
Which operating system/environment are you running PnP PowerShell on?
Beta Was this translation helpful? Give feedback.
All reactions