Hot answers tagged

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


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

I think that's the default behavior of publishing content types (as a whole, I think that's the idea), I don't know a way to publish the content type excluding columns, so my recommendation is unsubscribe your special subsite from the Content Type Hub or everytime you publish your content type it'll erase your special choices and you'll have to recreate it ...


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

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

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

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

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

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



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