Tag Info

Hot answers tagged

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


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



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