As a solution for that, the code below maps the Lookup field values into Taxonomy field values, aka Managed Metadata field values.
Note: The code above is very well commented, so no comments. Reference: Marcel Medina Click here to read the same content in Portuguese.
In this quick note I want to show you guys an example of how to work with the new object model for the migration of field values (Lookup fields X Taxonomy fields).
Consider the following Lookup List and Term Store in this example, that contains the World Cup 2010 Brazilian football players, according to Figure 1: Figure 1 – Lookup List vs Taxonomy Term Store Note: As you can see, the decision in migrating Lookup fields to Taxonomy fields is a battle. In my case as I am creating a Content Type Hub, all the Site Columns must not have dependencies, so a solution is to get rid of Lookup fields.
Okay fine, workflows are still out of box, what are we doing new in that? Imagine what would happen after a document (like our Functional Spec) is approved? Until the document is approved again it would no longer be in ‘Published’ state.
To view the previous state would be slightly messy.
The second problem was due to the missing Tax Catch All and Tax Catch All Label columns and missing event receivers on the list definition.
If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.
In this article we’ll continue where we left off and see how we can add a hook in Share Point and enhance the content creation and approval process to make it more valuable to end users.
In Share Point 2013 and Office 365 this functionality is gone.
You can still use different Java Script hacks (i.e.