Contents
SharePoint Foundation never writes changes that are made to a content type back to the content type definition file. Instead, it stores updates that are made to content types as entries in the SharePoint Foundation database.
Hidden content types are not displayed on the New menu for list views. Therefore, users cannot create items of that content type from the list. For more information, see Content Type Access Control. SharePoint Foundation never writes changes that are made to a content type back to the content type definition file.
How do you change the content type in a list?
Go to the list or library in which you want to change the content type. Do one of the following: If you are working in a list, click the List tab, and then click List Settings. If you are working in a library, click the Library tab, and then click Library Settings.
How are content types stored in SharePoint Foundation?
All list content types are stored as entries in the SharePoint Foundation database because when you add a site content type to a list, SharePoint Foundation copies a site content type locally to the list as a list content type. For more information, see Site and List Content Types.
Is it possible to update a sealed content type?
Sealed content types cannot be updated through the user interface or object model. If you must make updates to a sealed content type, you must set the Sealed property of the content type to false, and then make your changes.
Do you need to update the Content Type Definition File?
Do not, under any circumstances, update the content type definition file for a content type after you install and activate that content type. SharePoint Foundation does not track all the changes that are made to the content type definition file.
What does it mean to push down content types in SharePoint?
This enables SharePoint Foundation to propagate, or push down, changes that are made to a parent content type to its child site and list content types. When you make changes to a site content type, you can choose to push down those changes to all of its child content types.