The Content Type Hub (CTH) brings fantastic new functionality to SharePoint 2010, functionality that anyone who has delivered or administered SharePoint 2007 will have been crying out for and no doubt welcomed with open arms.
The CTH can be a complex beast with settings located in lots of different places; Central Administration, Site Collections, sub-sites and the CTH itself.
Chances are, by the time you get to using content types from the CTH in document libraries way down in the basement of your SharePoint site structures it’s been a long time since you set up the Managed Metadata Service and the Hub – or perhaps you are an Information Manager and didn’t set it up in the first place.
So my question is: Where would you start to look if your content types in sub-sites and lists refuse to update properly?
Now I’m presuming here that you have correctly published the offending content type in the Hub, have run the 2 timer jobs in Central Administration and that the Site Collection you are trying to push the content type to is consuming the CTH.
In fact, I’m assuming you have one or more content type from the hub on your consuming Site Collection and have added them to document libraries – but now you’ve decided you need a new column on one of the content types.
You go through the same process described above (publishing the content type in the Hub, running the CA timer jobs etc.) but when you come to check the document library there is no new column.
To reassure yourself that you’ve done everything correctly, you look at the content type gallery in the consuming Site Collection and can see the new column. Very strange!
You’d be forgiven for thinking “this must be a setting in the document library”, or perhaps you forgot to tick the ‘Update all content types inheriting from this type?’ check box in the ‘Update Sites and Lists’ section of the content type in the Hub.
So you check and you check to no avail. You may even have tried running some PowerShell scripts to force the update. Nothing!
So what to do?
Turns out it’s simply the way the Managed Metadata Service Connection has been set up.
There are four useful little tick boxes, which you’re only likely to see at the point you create the service, two of which have a huge effect on how the Content Type Hub functions.
To get to them go to Central Administration > Application Management > Manage Service Applications > Highlight the ‘Metadata Service Application Proxy’ (click anywhere but the title) > Select ‘Properties’ on the ribbon (see screen shot below).
This should bring up the ‘Edit Managed Metadata Service Connection’ window.
Here you can see the four options I was talking about.
The first two are firmly aimed at the Term Store, but the last two have a huge impact on the CTH functionality as I mentioned. The last one is clearly what we’re after so let’s tick that box!
You should now see your document libraries and lists updating from the CTH without a problem.
As you can see, this can be a difficult problem to track down because the Site Collections are getting the content type updates as they should be, just not in the lists – but as ever, there’s just one more check box!












