Wss3sdk: Update sub-content type

Each content type contains a reference to the website content type it is based on. This allows WSS to spread, or push changes to the parent content type to its subwebsite or list content type.
After you modify a content type, you can push these changes to all sub-levels. When the push operation copies the content to a website or list based on the content type, it does not overwrite the entire content type. On the contrary, the coverage scope varies depending on the user interface or object model.
Update sub-content types on the user interface

After you edit a website content type on the user interface and modify the content type settings page, all settings contained in the page are overwritten by push. Therefore, the granularity of our push is determined by the settings of the group on each page. Every time you make any changes on the content type settings page, all the settings on this page will be overwritten in the push operation.

The following is a summary of the settings on the content type settings page:

• Advanced SettingsThis page contains the following settings:

  • Document Template URL

  • Document Template file. If you select an existing template on your website or upload a template

  • Read-only attribute
• Create column settingsThis page is used to manage the columns created to the content type.

• Column settingsThis page contains the following settings:

  • Required

  • Hide
  • Remove a column from the content type

Update sub-content type through Object Model

The object model I push operation provides a coarse granularity. After we change the content type of a website through the object model,CodeActually, it only changes the performance of the content type in the memory. Only when the update method is called will the WSS submit these changes to the website database.

In the following example, two columns are added to the content type specification of a website by code, and the changes are pushed to all subcontent types.

C #

Spweb = Getspweb ();
Spcontenttype myct = Web. contenttypes [ " Specification " ];
Myct. Fields. Add (field1 );
Myct. Fields. Add (field2 );
Myct. Update ();
Update the custom settings to the sub-content type

You can also push custom settings through the object model at the granularity of the XML document. Each content type has an XML document set. A third-party solution can be used to store custom settings. We can overwrite specific XML documents through push operations. Note that WSS does not determine whether the XML document is being used or whether it is necessary for other procedures before overwriting. You can also delete the entire XML document in the push operation.

Considerations when updating sub-content types

You must know that the push operation will overwrite the changes made to the sub-content type, if these changes fall within the scope of the push operation granularity. For example, assume that you have changed the column in The subcontent type. If you subsequently make other changes to the column in the parent content type, or even delete the column and push the changes, Windows SharePoint Services overwrites you (or more likely others) the original change in the subcontent type.

Each push operation only pushes this change to the parent content type. If you do not push the changes, you cannot easily push them later. In most cases, you can only be forced to cancel the previous changes, and then change them again, and then push them again. For example, if you delete a column from the parent content type, this change is not pushed at the time. Any subsequent push operations do not include deleting the column from the sub-content type. If you want to delete a column from the Child content type, you need to re-Add the column in the parent content type, delete it again, and then perform the push operation.

If the changes you push no longer apply to the sub-content type, these changes will be ignored. For example, if you change the top of the push bar to a column that has been deleted from the sub-content type, these changes will be ignored. Windows SharePoint Services does not add the column back to the sub-content type.

If you try to push the content marked as read-only sub-content, the push operation will fail unless you set the parent content type to read/write in the push operation).

The push change is not an all-in-one or all-in-one operation. If the push change fails for a sub-content type, Windows SharePoint
Services will continue to push changes to any remaining sub-content types. Windows SharePoint
Services returns a list of errors in the process.

If the sub-content type is defined as sealed, the push operation fails on the content type.

Note::

To create or manage a website content type, you must be at least the website designer of the website. If you do not have proper access permissions for some sub-websites, the push operation will fail on the content types of these sub-websites.