Jun 03 2019 02:42 PM
Working on adding all company document types to the Content Type hub so that the content types will be available once we create new project sites.
For some reason there is a column "Type" that can not be added because the system says it's already in use or is reserved. I can not find the column to use it and I can not add it. Am I missing something? Where can I find this column or is there a work around? Any help would be greatly appreciated! :)
Jun 03 2019 07:28 PM
@Chiara Gomez I am pretty sure Type is used for the file type (Word, PowerPoint, etc.). If you need a similar custom column, you just need to find a different name.
Jun 03 2019 09:07 PM - edited Jun 03 2019 09:18 PM
SolutionHi @Chiara Gomez,
Depending on how you are creating your Site Column, the Internal name must be unique.
Option #1 - User Interface
Note: the U.I. will not let you rename the column to "Location", the message will say "The column name that you entered is already in use or reserved. Choose another". PowerShell does not have this limitation...
Option #2 - PowerShell
Setting the internal name using the PnP PowerShell cmdlet is easy, please see the example below adapted from Microsoft documentation:
Add-PnPField -List "Demo list" -DisplayName "Location" -InternalName "MyCompanyLocation" -Type Choice -Group "Demo Group" -AddToDefaultView -Choices "Stockholm","Helsinki","Oslo"
https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpfield?view=sharepoint-ps
In your case, @Chiara Gomez, I would give your column an internal name of DocumentType or MyCompanyDocumentType and set the display name to something more friendly...
Jun 04 2019 02:40 PM
Jun 04 2019 02:46 PM
Jun 03 2019 09:07 PM - edited Jun 03 2019 09:18 PM
SolutionHi @Chiara Gomez,
Depending on how you are creating your Site Column, the Internal name must be unique.
Option #1 - User Interface
Note: the U.I. will not let you rename the column to "Location", the message will say "The column name that you entered is already in use or reserved. Choose another". PowerShell does not have this limitation...
Option #2 - PowerShell
Setting the internal name using the PnP PowerShell cmdlet is easy, please see the example below adapted from Microsoft documentation:
Add-PnPField -List "Demo list" -DisplayName "Location" -InternalName "MyCompanyLocation" -Type Choice -Group "Demo Group" -AddToDefaultView -Choices "Stockholm","Helsinki","Oslo"
https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/add-pnpfield?view=sharepoint-ps
In your case, @Chiara Gomez, I would give your column an internal name of DocumentType or MyCompanyDocumentType and set the display name to something more friendly...