Forum Discussion
Site columns not inheriting from Content Type Hub
- Oct 23, 2023
Sam_C1610 The content type hub allows you to share Content Types across your tenant. Since a content type can have columns, the only way you can share columns is when they are used in a Content Type. Columns are not "pushed" to your sites on their own. See: Publish a content type from a content publishing hub - Microsoft Support. You can, however, share column values by creating term sets (managed metadata values) at the "root" of your tenant and then in each site, pointing site columns to those term sets. The link you are referencing is a little misleading. It's not technically inaccurate, but it doesn't provide the entire story.
Sam_C1610 The content type hub allows you to share Content Types across your tenant. Since a content type can have columns, the only way you can share columns is when they are used in a Content Type. Columns are not "pushed" to your sites on their own. See: Publish a content type from a content publishing hub - Microsoft Support. You can, however, share column values by creating term sets (managed metadata values) at the "root" of your tenant and then in each site, pointing site columns to those term sets. The link you are referencing is a little misleading. It's not technically inaccurate, but it doesn't provide the entire story.
I should probably have described the wider picture of what I'm trying to do: I want to extend every 'Site Pages' document library within the tenant to have some common columns such as "review date" and "review schedule". I thought at first I'd just create these as shared columns within the Content Type Hub.
However, if I have to add to a content type (I've made one called "Org Site Page", inheriting from "Site Page"), how can I make this what's created whenever someone wants to add a new page to a site? I can see that it's not just looking at the default for the library as this is still set to the "Wiki Page" content type.