Tag Info

Firstly, you need to know that Managed Metadata Service can be responsible as a Content Type Hub. Content Type Hub is a location where you can manage and publish content type across site collection, web application and farm. One more terminology you need to know is Content Type Subscriber, which will subscribe to Content Type Hub. Once you publish Content ...

Yes, you create a site collection for the hub and activate the Content Type Syndication Hub feature at the site collection level. There is a timer job that runs which will essentially copy the content types from the hub to the subscribing site collections. If you need a content type change immediately then you can start the timer job manually. Note that ...

This has to do with how SharePoint "builds" content types I think. It needs to know where to find the parent, or more specifically, the parent's original schema (XML). If Inherits is set to true, it will include the parent's fields directly in its own schema, when this is not the case. it will always require a schema to be based on, which can be found in the ...

Hi Here is a example how to create a custom content type and add it to 365 ClientContext clientContext = new ClientContext("http://anmol-pc"); Web web = clientContext.Web; ContentTypeCollection contentTypes = web.ContentTypes; clientContext.Load(contentTypes); clientContext.ExecuteQuery(); ContentTypeCreationInformation newConInfo = new ...

I had changed a field definition's property and found that the new definition was synced to the subscribing site after also republishing a content type that was using the customized site column. I did this on SharePoint 2010, and only had one content type that was using the customized site column. In this case I had changed a Date/Time field's default value ...

It's recommended to create a unique site collection to act as your content type hub. This allows for separation from your normal users and day-to-day activities. When working on a content type, there is an option to publish it, and then republish it after an update. Updates do not automatically go out if a CT is updated. Also keep in mind the Content Type ...

There is no documented limits on number of contenttypes. SharePoint limits are documented in SharePoint Server 2010 capacity management: Software boundaries and limits. But be aware that it'll take some time for all of the content types to be available when you create new site collections. But another question is what you expect to get as benefit from ...

There is an Content Type Hub FAQ which addresses the CT Hub construct but the limitation would be based on the list that uses the content type and the number of list columns - SharePoint 2010 Column Limit (based on column type).

Use a standard Site Collection in an existing Web App (don't waste resources on its own Web App). Also carefully consider the template to use - you might need different features to deploy your content types. Also do not use the Blank template. I normally use a std Team Site and then activate the necessary features.

From a technical point of view it doesn't matter how you create it. But usually I wouldn't use an entire Web Application for it. And I'd also not "waste" the root on it. The only thing to really make sure is that you only use that site collection as Content Type Hub and nothing else. Again not due to technical reasons, just to make sure you only give ...

I don't think client side object model is a good idea. I think you need to publish them using code written in a feature receiver. Please see the link below... http://blogs.msdn.com/b/chaks/archive/2011/09/04/content-type-hub-publishing-and-subscribing-to-content-types-programmatically-c-code.aspx

I know this really should not be an answer, and should be a comment on the accepted answer, but apparently I cannot add a comment. In any case, I have a potential solution to the problem of the Inherits attribute, and needing to set it to True so you can publish content types correctly vs. needing to set it to False so that you can preserve your declarative ...

Because you can still utilize content types in addition to hubs, I don't think it is fair to list these as pitfalls, but maybe slight limitations. Workflows are not supported at the HUB (WF can be attached to list/library where content types are utilized) Content Types deployed as features to the HUB require the same feature be activated on sites ...

I had the issue where some site collections would receive the content types, while others would not. This is what finally solved my problem: Central Admin/Application Management/Configure Service Application Associations Select the appropriate Application Proxy Group Uncheck the MMS thats having issues and click OK Wait a couple of minutes Select the ...