SharePoint Config

This article contains Details on how to configure npm to work behind a proxy server that uses NTLM authentication.

SharePoint allows you to publish SharePoint links so that they appear in Office ‘Save As’ dialog boxes. This is useful if you want to encourage users to save Word, Excel and other Office documents directly into SharePoint rather than the file system as this dialog is shown the first time you save a new file. It allows you to create targeted shortcuts so relevant document libraries and sites are easily accessible when saving Office documents.

In SharePoint 2010 these published links are managed under the user profile service application in a page called ‘Published links to Office client applications’.

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.

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.

Default Column Values

SharePoint 2010 has some great document management enhancements. One of these is the ability to set location based metadata defaults. This allows you to specify default metadata for documents based on the document library or folder they are uploaded to (i.e. a document could be automatically tagged with Subject=Legal when uploaded to one folder or Subject=Finance if uploaded to another). This is especially useful in situations where users are bulk adding documents that need to have the same metadata applied.

The Problem

I was showing a developer this feature recently when I noticed that on one particular library the column default settings were not applied. The settings were available and I could set the properties correctly using the default column values page but when we tried… Continue reading SharePoint 2010 column default values missing »

The SharePoint 2010 Health Analyzer provides a great way of identifying installation problems but it can take days or weeks before a full set of results appear. When installing a new environment it can be helpful to get instant feedback on any health issues so they can be resolved before users start using the environment. This post shows you how to run all the health analysis rules instantly using PowerShell so you get an instant health check.

This post describes how to use the ContentTypeBinding element to avoid an error that can occur creating publishing pages. Continue reading Error creating SharePoint publishing pages »

If you have an ASP.NET control that contains validation controls in the masterpage or page layout for a publishing site (an ASP.NET login control for example). When you try to edit and check in a publishing page you receive the following error.

This page contains content or formatting that is not valid. You can find more information in the affected sections. Continue reading ASP.NET validation controls prevent publishing pages from saving »

Something that I wasn’t aware of until now is the fact that if you save a site template in MOSS 2007 it will not work in WSS 3.0. Continue reading MOSS Site Templates Not Compatible With WSS »

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 »