Itemupdating

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.I’ve based the code on Wictor’s excellent example with a couple of minor updates.Instead of hardcoding the name of the term store I’m getting the default keyword store associated with the site (this means we do not have to hardcode the name of the managed metadata service but you should check this works in all your environments).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.In Share Point 2013 and Office 365 this functionality is gone.You can still use different Java Script hacks (i.e.

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.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.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.

Leave a Reply