Itemupdating

Hi, my name is Rob Howard, and I’m a Program Manager with the Share Point Designer team.Like several of the other people posting here, I also built many of the Application Templates for Windows Share Point Services.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”).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.get Tag From Identifier And Title The most important part of our solution is the “get Tag From Identifier” function.

itemupdating-53itemupdating-20itemupdating-43itemupdating-1

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.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).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.With this information we can use the following steps to deploy managed metadata fields that avoid these issues.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.

Leave a Reply