Hot answers tagged

11

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


5

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

I fixed my issue by creating a new site collection to serve as the content type hub, then changing the metadata service to point to that new site collection for the hub property http://www.sharepointanalysthq.com/2010/11/how-to-change-the-content-type-hub-url/ I believe my original issue was due to me not waiting for the "content type hub" timer job to ...


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


4

This article fixed my issue: The cause of all this trouble is a permission issue. More precisely a permission issue on the TaxonomyHiddenList. The TaxonomyHiddenList list can be viewed by navigating to /Lists/TaxonomyHiddenList/AllItems.aspx. This list contains the details of all of the terms that are used in any managed metadata column. When ...


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

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


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

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


2

One reason to beware of many content types is the impact it has on general site collection creation times. Each time a new site collection is created, all syndicated content types in connected hubs are copied down to it. So the more content types you have the slower it becomes to create site collections. In our staging environment, we found that once we ...


2

I just ran into this issue. While watching the SharePoint logs I found that the field in question was added locally to the site columns instead of added using the content type hub. So when trying to update the content type there was an error due to two columns with the same name (the one at the content type hub and the one local). The fix was to delete the ...


2

In addition to republishing the content types from the hub, you will need to go into every subscriber (consuming) site collection -> content type publishing -> Refresh all content types. On this page you also have the option to view the error log - this will show you which content types could not be consumed and why. Usually it's because of a column name ...


2

You shouldn't have any issues by updating the template. Just make the change in your content type hub and re-publish the content types. Documents that were created with the old template will not be updated to target the new template though. If that has to happen, they need to be updated manually.


2

So if this is happening to you you should first publish your content type, at your content type hub. From there you should click "Manage publishing for this content type" and you will see 3 options: Publish Make this content type available for download for all Web Applications (and Site Collections) consuming content types from this location. Unpublish ...


2

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


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/


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

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


2

The Content Type Hub will not be visible in the sitecollection listing. But however you can access it from https://mydomain.sharepoint.com/sites/contentTypeHub


2

Couple of things to check: Make sure that MMS proxy associated with the web app.( Central admin > Application management > web app and from ribbon select service connection) Also check if MMS services is running on at least one server in the farm.( Central admin > Managed Services on server.) Also browse the MMS from central admin and see if it working ...


2

You would need to create a site collection scoped feature that would create them and add them to the content type gallery if you are not going to use a content type hub. This makes upkeep much more complex, so I'd encourage the use of a hub if possible.


1

Lookup columns will only lookup data in lists in the same site/web. When the content type hub functionality deploys your content type to other sites, the lookup list does not exist there, so the column is removed. The best way to do this is to use a managed metadata term set instead. The term set is globally available to all site collections. So you can add ...


1

Alternatively, you can provision your lookup column with a feature receiver everytime you create a new website. You just need to make sure you have the lookup list available somewhere (which, by the way, CAN BE in a different web site). There is a quick and easy to implement guide which you can find here: ...


1

I think it would be best to have them follow a standard naming convention for the Content Type names, like VendorName(or abbrev) Document, VendorName Project, etc and use separate groups. They could then use a singular CT hub and would reduce collisions. This gives total visibility to everyone and can help with governing it too. I would fear that if it was ...


1

Your interpretation is correct. A Managed Metadata Service application can be used to share content types across site collections by associating a Content Type Hub with it. A content type hub site is generally created as it's own site collection and is purely used to store custom site columns and content types and publish these to subscribing site ...


1

The data from your old hub lives on in the Managed Metadata Service Application database. The nuclear option would be to delete and recreate your MMD service application to totally purge the data. If this is a production system and you have term sets already in use, you are going to have to recreate that as well, including the GUIDs on all objects.


1

it is not visible but default content type is their and can be access via site collection named /sites/contentTypeHub. But here is one issue. only the original Office 365 account creator has access to the site collection. Accessing it with another user will get you an access denied error message even if you are a global administrator. fix: Unfortunately, ...


1

This is how i fixed it. In Central Admin > Manage Service Applications > Managed Metadata Service (The Service Connection, not just the service) > Highlight and Click Properties. At this point you have 4 check boxes. This service application is the default storage location for Keywords. This service application is the default storage location for ...


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

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



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