Friday, 23 August 2013

SharePoint Document Sets - not to be confused with FOLDERS

Document Sets - in my view is a very misunderstood and commonly misused entity in SharePoint.
The general perception about Document Sets is that they are Folders with a Welcome Page, but there is much more to it than just that.
A Document Set is a separate entity while a Folder, more or less, behaves as a location. Therefore, apart from grouping related items together a Document Set can also be treated as an item in a SharePoint Library. Therefore, all operations that are applied to a SharePoint Library item can be applied to a Document Set.
Below is a list of features of Document Sets:
  • A Document Set contains a welcome page which can be used to give more information about what it contains. Web Parts can be added to the welcome page to give a snapshot of what the Document Set will contain.
  • It can contain separate Metadata and Site Columns from the Library in which it is contained. Metadata and Site Columns can be shared by all documents in the Document Set or can be applied to individual documents.
  • By creating Content Types inherited from Document Set, we can define default documents that will be created along with our new Content Type. Suppose, we define a Content Type for Sales Report then we can associate all Sales Reports templates with that Content Type. Each time a new Sales Report Document Set is created, all the templates will be created along with it and users can simply fill in those templates to generate their report.
  • Workflows can be associated with the entire Document Set or individual documents inside the Document Set
  • Versioning can be applied to the Document Set.
  • Specific content types can be made allowable inside a Document Set.
  • Unique permissions can be associated with a Document Set.
Below are a couple of features not available with a Document Set, when compared with a Folder:
  • Document Sets cannot be nested i.e. Document Sets cannot contain Document Sets
  • Document Sets, as the name clearly suggests, cannot be associated with SharePoint Lists.
To enable Document Sets within your site you need to activate the Document Set feature which is available at the site collection level.

Document Sets are not available with SharePoint Foundation 2010.

Below are certain links for further reading:
For limitations of Document Sets refer this link:


Monday, 12 August 2013

Configure LDAP Authentication for your SharePoint 2010 or 2013 site

Recently, I tried configuring LDAP authentication for my SharePoint 2013 application.

Obviously, in case of SharePoint 2013 we need to use Claims based authentication and we need to configure three configuration files:
  • Security Token Service web.config
  • Central Administration web.config
  • The specific web application web.config.
There are many blogs explaining the details of these configurations. Here is an interesting link that explains stuff in detail -

However, there is one important task that you need to perform on your LDAP server to ensure that the authentication is successful. You need to give administrative permissions to the following accounts on your LDAP server:
  • Security Token Service application pool account
  • Central Administration application pool account
  • Web application app pool account.
This simple task had me hung up for quite a few hours (or days, I can't really recollect).

The interesting thing here is that SharePoint does not give you the specific error that it cannot access the LDAP directory straight away. It throws in a lot of generic errors such as - User credentials cannot be authenticated, please check user name and password. And somewhere amongst these generic errors is hidden your real error that it cannot access the LDAP server objects for authentication.