Consider the following scenario:
You have multiple custom content types that are based on a document content type. These custom content types are published from a content type hub site collection to subscriber site collections.
On a subscriber site collection, you set one of the custom content types as the default content type on a document library.
You enable the Document ID Service feature on the site collection.
When you go to the site collection and then view a document in a document library, the document IDs aren't assigned, and the document ID column isn't displayed as a column in a view.
To enable the Document ID Service feature on a site collection that's subscribed to the content type hub, you must first enable the Document ID Service feature on the content type hub site collection. Then, you must republish syndicated content types so that the subscriber site collections can update their site content types.
For more information about how to publish a content type from a content type publishing hub, see Publish a content type from a content publishing hub.
This issue occurs because a site content type that's published to a subscriber site collection is set to read-only when a content type hub publishes a content type. This occurs regardless of whether the content type that's defined on the content type hub is read-only. When the Document ID Service feature is enabled on the subscriber site collection, required columns are missing and cannot be provisioned because the site content type is read-only.
For more information about how to enable site collection features, see Enable or disable site collection features.
Still need help? Go to Microsoft Community.