3

I created one content type called client in the content type hub. THen I created another content type called project on the content type hub, this one should have a lookup column to the client.

As the list does not exist, I created it in the content type hub.

I also created the list for clients in the content type hub, I exported both lists as templates (STP)

Then I created the lists based on the templates on the destination site collection, client list works perfect.

However project list does not work, it says the list does not found (the lookup list), I had to manually delete the lookup column on the destination content type, and add it again.

This is not a nice solution, and I guess if the content type project is published again, then I will lose my changes over and over.

Any nice solution to this problem?

  • Converting lookup to managed term set is the best option. – Amal Hashim Jan 5 '15 at 21:39
  • +1 nice idea! :) – Luis Valencia Jan 5 '15 at 22:06
3

Instead of lookup use a Managed Metadata Term field.

A Managed Metadata column is a can be added to content types to enable site users to select values from a specific term set of managed terms and apply these values to their content. You can create and configure a Managed Metadata column to map to an existing term set or term, or you can create a new term set specifically for a Managed Metadata column.

More information https://support.office.com/en-ie/article/Create-a-Managed-Metadata-column-8fad9e35-a618-4400-b3c7-46f02785d27f

  • if I use managed metadata field, for client name for example, the term is saved into the group for the content type hub – Luis Valencia Jan 5 '15 at 22:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.