I’m taking the code approach here as it is the only way to ensure the field will work across multiple environments.
I’ve based the code on Wictor’s excellent example with a couple of minor updates.
With this information we can use the following steps to deploy managed metadata fields that avoid these issues.
I’ve also created an example project that I’ve included at the end of the article if you want to see this working for yourself.
The first part of this two part series discussed some of the problems with provisioning Share Point 2010 managed metadata fields.
This and the following step is often missed out in other articles but cause problems if you try to create custom list definitions that include the managed metadata column. The problem stems from the fact that Share Point is looking for an associated note (i.e.
The specific error message you get is: Error – Failed to get value of the “” column from the “Managed Metadata” field type control. text) field that is required for the metadata column to work.
This post will cover a robust method of deploying Share Point 2010 managed metadata columns in a way that avoids common errors and enables the columns to automatically show up in the search refinement panel.
To recap on the previous post we are aiming to avoid the following problems when creating Share Point 2010 taxonomy fields through features: We found the first problem was due to a missing note field when creating a list definition that used the site column.