Tag Info

Hot answers tagged

9

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 ...


4

You don't need a content type hub with a single site collection. The benefit of the hub comes into play when you have multiple site collections in the same Web Application that share content types and you want to manage all of the content type updates in a single place (the hub).


4

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 ...


3

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 ...


3

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 ...


2

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 ...


2

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 ...


2

A site collection subscribes to the hub. So in your scenario, the three subscribe and the seven do not. http://blogs.msdn.com/b/chaks/archive/tags/cthub/


1

I don't know if you still face this problem, but I just had the same problem and the solution might be of use to others as well. It appears to be due to the content type being created in an Enlish site (/sites/contenttypehub), and being succesfully published to (and showing up in) our English team site (/), but not to the Dutch subsite /vaktechniek. After I ...


1

Your sub sites will have the content types. Make sure that you have created the content types, and the hub, on the root site. You know that you are on the root site because if you go to site settings, you will see the "Site Collection Administration". Really the only possibility is that the hub is not coming from the root site of the site collection (I ...


1

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


1

When a timer job instance is created, it is persisted to the farm configuration database. Accessing this database for write purposes is a privileged operation; as a rule of thumb, only the farm service account (that is, the account under which OWSTIMER.EXE executes) or accounts that explicitly have the rights required to carry out such an ...


1

It's not enough to add TaxKeyword to your content type/list, you have to add TaxKeywordTaxHTField as well. This one is a hidden field but neccessary to get the keyword-field working. But it doesn't stay persistent within the item. After saving, it's gone again. Except when done the following: ...


1

The Document ID Service feature is enabled at the site collection level. Whether or not that site collection consumes content types from a hub is irrelevant. The document ID will get a prefix unique to the site collection (which can be changed). When the Document ID Service feature is enabled, the document ID column will be added to all documents created ...


1

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 ...


1

I have this little powershell function you can try it out... function SetManagedMetadaService { Param( [parameter(Mandatory=$true)][string]$ServiceName, [parameter(Mandatory=$true)][string]$HubSiteUrl ) Write-Host "Setting contenttype hub Url" #Get-SPServiceApplication | ForEach-Object { # if ...


1

You can change it via PowerShell. See this article: http://www.sharepointanalysthq.com/2010/11/how-to-change-the-content-type-hub-url/ They basically show how to use this cmdlet: Set-SPMetadataServiceApplication -Identity "<ServiceApplication>" -HubURI "<HubURI>"


1

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 ...


1

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 ...


1

Deleting content types from the hub orphans them in the spokes. The technique I use is to delete the content types from the spokes first (you'll have to set ReadOnly = false before deleting) then un-publish the content type in the hub and then delete the content type from the hub.


1

Irrelevant of the Content Type hub, working with look-up columns can be tricky. You either create them declaratively (at the time of Content Type deployment) - which also assumes the list you are targeting is already there (or self-referencing -the same way the Tasks or Issues list work) or use code, say during a FeatureActivated handler where you could ...


1

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 ...


1

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).


1

Since you are effectively changing the list schema, you may have to do an oSPList.Update() as well.


1

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.


1

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible