This is another step that isn’t always mentioned but if this feature is not present then you are presented with a greyed out metadata selection when adding or editing items (note this also happens if the field is not connected to a term set).
You won’t get any obvious error messages and the feature is hidden so you won’t see it in the site features list either.
So to create this note field we can add a field similar to the following: Note: Share Point uses the suffix _0 appended to the display name of the field and Tax HTField0 after the static name so I’m following those conventions.
To link the two together we can update the field we created in step one to include a customization section that points to the note field as shown below: Note the value within the Text Field property is the ID of the note field we created above.
The last issue can be easily avoided by adding a feature dependency to ensure the required feature is activated before we deploy our custom site column.
With this information we can use the following steps to deploy managed metadata fields that avoid these issues.
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.
I’ve also added in some additional error handling so we get informative messages if the metadata service and/or term set does not exist.
Note that if we are only creating a site column (or even a content type) this should work without completing the following steps.
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.
If we inspect a list that contains a managed metadata field created through the UI it shows two event receivers.