SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

We need to customize newdocset.aspx of document set in SharePoint 2010. Currently reference is given to newdocset.aspx of _layouts folders application pages. Did lot of research, but I got no where.

share|improve this question

migrated from Feb 15 '13 at 15:23

This question came from our site for professional and enthusiast programmers.

marked as duplicate by Robert Lindgren Apr 13 at 15:09

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Microsoft has a sample of how to do this on MSDN. You would basically create an Application Page that serves the same function and then set the "new" url of the document set content type (or your custom one build on it) to that new page:

share|improve this answer

My team and I have found a custom solution that does not require a new feature or application page.

Using SharePoint Designer, create a new Edit form at the target Library. For this example, we'll call this form CustomNewDocSet.aspx

In SharePoint Designer, navigate to a List and create a New Form of type New item form. Then, take that markup and place it into "CustomDocSet.aspx". This will update the 'Type' of this form from Edit to New. At this point, you associate this form with the target Library's Document Set content type as the "New Form". Upon creating a New Doc set, you should be routed to CustomDocSet.aspx and realized there were no Save or Cancel buttons!

You can add these buttons adding the following snippet between the & tags:

Afterwards, navigate to the CustomDocSet.aspx page and Edit the page to add a Script Editor webpart for any custom .css and .js

So far so good, as I have not encountered any nuances or issues with this implementation.

share|improve this answer