Forum Discussion
Modify base content type
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.
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.
- Hi Matt, that would still give you problems with list templates and site templates. Yes you could update these but it just makes things difficult for the normal user. This is one of the reasons why in quite a few situations creating apps is better that manually using lists in SharePoint. And even without content types sometimes works
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
http://download.microsoft.com/download/6/3/5/635302D8-FE1F-4A33-94A0-CFABBF2C5930/oit2010-whitepaper-sharepoint-content-types-best-practices.docx
