Nov 02 2017 09:58 AM
Hi
What are the risks involved in modifying a SharePoint base content type - eg document?
Is there any official Microsoft guidance on this?
many thanks in advance
Nov 02 2017 10:07 AM
Hi @Jon Lyall,
I wouldn't!
If you add a field called "VeryImportant" and Microsoft adds a field "VeryImportant" in the future then you might find that you get some trouble. It would be better to create a new content type called "Company Document", although I've seen in the past this creating a managerial mess too as you will need to update the content type every time you create a new library.
I wonder if this is the reason why Microsoft is making it easier to add new list columns on modern lists and with this ignoring the whole content type model.
Nov 02 2017 10:46 AM
Jon, in addition to creating a new content type as Pieter suggested, you also have the ability of removing the default content type from a library after adding another one in. If there's something about the default content type that you don't like, that'd be the way to "remove" it.
Nov 02 2017 11:43 AM
Nov 03 2017 01:11 AM
Thanks all for the replys.
I was looking for MS guidance around the risks involved in modifying a base OOTB content type.
found it here for reference
Nov 03 2017 01:24 AM
Nov 03 2017 01:49 AM - edited Nov 03 2017 01:50 AM
And in case you modify the default content type and in future you need support from Microsoft then it may be a challenge as you modified content type against the Microsoft guidelines. So, its better to create a copy of the default content type.