Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I created a large sharepoint 2010 collection which we are trying to clone throughout the company. Although we have some issues (like MMD disappearing, and Reusable workflows not being automatically applied), these are things we can fix after cloning.

The real issue we have now is that Document Sets don't seem to function correctly.

In the original collection, we created 3 document sets and applied one of them to a library. In the Clone, that document set in the original library functions properly.

However, any new document set content types added to that first library, and any time we re-apply the single working document set to a new library, doesn't work properly.

When ever we create a new test document set "item", it seems to be created correctly... you are instantly taken to the document set home page (with /Forms/DocSetType/docsethomepage.aspx in the URL). However, once I navigate back to the library view and try to re-open the new document set again, it looks and functions like a folder (with /Forms/AllItems.aspx in the URL instead of the doc set home page).

So to recap:

Any library already associated with a document set before cloning works with the original doc set content type. Associating a new doc set with the same library gives the error. Associating the "working" doc set content type with a new or other existing library also gives an error. Creating any new doc set content type from scracth also creates the error If we create a library template from the working library with the one content type, it seems to work the same way...only the original doc set content type functions properly. So if it was created and associated with a library prior to cloning, it works, any doc set content type created or associated to a library after cloning gives the same error.

Any help is greatly appreciated

share|improve this question
    
I have the same issue it seems. The document sets that used to work on the server prior to cloning no longer works, but I have tested it and it still works on the cloned machine though. Have you resolved this problem? –  user17027 May 15 '13 at 15:33
add comment

migrated from stackoverflow.com Jan 21 '13 at 16:03

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

2 Answers

Try this:

  • open context menu from document set that is not working
  • choose "Edit properties"
  • check "content type" and if it is Folder change it to Document set

I've had similar problem after creating document libraries with document sets from template and solvet it this way.

share|improve this answer
add comment

The ProgID has become disassociated from the Document Set. If you have access to SharePoint Manager (codeplex project) you can use it to inspect the item. If the ProgID field is empty enter SharePoint.DocumentSet and click "save" icon in the upper left corner. (There's probably a PowerShell way to accomplish this too without SM) enter image description here

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.