Fired event itemupdating which wasn t

section to the field and hardcode the various Id’s that define a term set (required if you are using a sandboxed solution), or configure these in code.I’m taking the code approach here as it is the only way to ensure the field will work across multiple environments.If we inspect a list that contains a managed metadata field created through the UI it shows two event receivers.These are the Taxonomy Item Synchronous Added Event Receiver for the Item Adding event and the Taxonomy Item Updating Event Receiver for the Item Updating event.I’ve based the code on Wictor’s excellent example with a couple of minor updates.

Montreal site xxx

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.At this point we have a robust way of deploying a standalone site column which is useful in certain situations but in many situations we need to provision content types, list definitions and list instances which is when things get tricky…As explained in the previous post Issues provisioning Share Point 2010 Managed Metadata fields – to ensure the metadata field automatically appears in the search refinement panel as it does for all other managed metadata fields we need to add the Tax Catch All columns to our list definition and wire up two taxonomy event receivers.When we add either the site column or content type to a list the managed metadata field works and shows up in the search refinement panel (at least it did in my testing).

This is due to the fact that Share Point automatically wires some extra bits (shown below) when the field is added.

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.