SharePoint Config

The first part of this two part series discussed some of the problems with provisioning SharePoint 2010 managed metadata fields. This post will cover a robust method of deploying SharePoint 2010 managed metadata columns in a way that avoids common errors and enables the columns to automatically show up in the search refinement panel.

To recap on the previous post we are aiming to avoid the following problems when creating SharePoint 2010 taxonomy fields through features:

1. If you create a list definition that uses this site column you get the error: Failed to get value of the “{0}” column from the “Managed Metadata” field type control. See details in log. Exception message: Invalid field name. {00000000-0000-0000-0000-000000000000}.
2. The managed metadata column does not appear in

If you are using the SharePoint object model to return list items, the items are security trimmed based on the rights of the user running the code. In most cases this is great, you don’t have to do any manipulation of the items returned from CAML queries to ensure users only see what they have access to. Continue reading Returning approved SharePoint list items from a console application »

Saving a list as a template is an easy way of transferring data from one place to another in SharePoint. By default, however, the maximum size of list templates in WSS 3.0 and MOSS 2007 is 10MB. Continue reading Increasing the maximum size of list templates »