SharePoint Config

There are a couple of issues with major versioning in SharePoint 2010 that prevent users saving files into document libraries. Things like this can be very frustrating for a client so it is worth being aware of these when designing SharePoint solutions in the hopes they are avoided. The issues are:

• Saving files from Office 2007 fails when a document library has major versioning enabled and contains a required field
• Copying files using Windows Explorer fails when a document library contains a required field and column default value settings for this field

I believe these are bugs with the product and both have been raised with Microsoft support so hopefully they are fixed in future updates. In the meantime this articles covers the details and some possible workarounds in case you run into the same issues.

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

I’ve been working with the managed metadata functionality provided in SharePoint 2010 fairly extensively over the past few months. While it is a great feature and works well when used through the UI it has several rough edges that can cause problems when you are deploying features that use managed metadata fields. Some of these have been documented elsewhere but some of these haven’t so this will be the first of two posts covering (1) some of the potential problems using managed metadata (this post), and (2) a robust way of provisioning SharePoint 2010 managed metadata fields.