Fired event itemupdating which wasn t there was a problem validating your software license phpmydirectory
At least in my testing when we create a list definition this isn’t all wired up correctly and the following steps were required.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.I find the easiest way to ensure all the columns are added to the list definition is to add them to a content type first.This content type should contain the managed metadata/taxonomy field, the note field and the Tax Catch All and Tax Catch All Label fields as shown below.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.
This is due to the fact that Share Point automatically wires some extra bits (shown below) when the field is added.
The first part of this two part series discussed some of the problems with provisioning Share Point 2010 managed metadata fields.
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.
This should be done as a separate web scoped feature.
All going well we will now have a list that contains a correctly functioning managed metadata field which automatically gets extracted during search processing and displayed in the search refinement panel as shown below.
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.