Event itemupdating which wasn

Sidenote: you want to remove the /Lists/ prefix from the URL when creating document libraries to avoid breaking the default column values feature.

You will also want to add in the file dialog view as it goes missing when using the Visual Studio 2010 tools.

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.

Create a managed metadata field The first step is to create a site column using the Field element with a Type of either Taxonomy Field Type (allowing a single selection) or Type Taxonomy Field Type Multi (allowing multiple selections if you also set Mult=”True”).

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

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.

We can do this first step using the Visual Studio 2010 tools to create a list definition from the content type we created earlier.

As we added the Tax Catch All columns to our content type these will automatically be added to our list definition.

Leave a Reply