Itemupdating event not

Rated 4.71/5 based on 613 customer reviews

I find the easiest way to ensure all the columns are added to the list definition is to add them to a content type first.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.To recap on the previous post we are aiming to avoid the following problems when creating Share Point 2010 taxonomy fields through features: We found the first problem was due to a missing note field when creating a list definition that used the site column.The second problem was due to the missing Tax Catch All and Tax Catch All Label columns and missing event receivers on the list definition.To add these to our custom list definition we use an element file similar to the one below (note the List Template Id should match the Type attribute of our list definition).As a final step we can optionally create a list instance so that when we deploy our solution lists are created automatically.

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

Leave a Reply