Tag Info

Hot answers tagged

5

No, there is no native web service that allows you to create a DocSet. You have to write code to do this. Two techniques: Use the client OM to create one: http://sharepointfieldnotes.blogspot.com/2010/02/how-to-create-document-set-remotely.html Use the server OM to create one: ...


5

In a way yes - try using the "Link to a document" content type instead of the document. or use the "Send To" option which would create a syncronized copy of the document (multiple locations possible) which can be easily maintained. In the case of Send To, yes, i believe -which should also answer your 3rd question (but if not) Hope it helps, C:\Marius


5

The SharePoint "Append Changes to Existing Text" column is a HACK implemented by the SharePoint team, in reality it's just an ordinary text field, but where the rendering is grapping the text from previous versions and using these to create what appears to be a functioning append text field. So the field is very dependend on the prior versions to exist (you ...


4

The url for the document set welcome page includes an ID in the query string, so you can use this parameter to find the document set: http://server/MyDocumentLibrary/Forms/MyDocumentSet/docsethomepage.aspx?ID=2 var id = Convert.ToInt32(HttpContext.Current.Request.QueryString["ID"]); SPListItem item = ...


4

OOTB the views are the same when displaying the list of document sets and displaying one document set with all the files in it. But you can set different views: Create a new view to use when displaying the files in the document set Go to the list settings and allow management of content types in Advanced Settings Select the Document Set contenttype In the ...


4

This has to do with how SharePoint "builds" content types I think. It needs to know where to find the parent, or more specifically, the parent's original schema (XML). If Inherits is set to true, it will include the parent's fields directly in its own schema, when this is not the case. it will always require a schema to be based on, which can be found in the ...


4

First of all there is no document set library in SharePoint. There is only a content type that is called "Document Set" and this can exists on certain document libraries. You need in to use in your declaration the RegistrationType="ContentType" and for the RegistrationId="0x0120D520". Last one is the id of the content Type "Document Set". The required ...


4

Link to document content type is what you want as Marius mentioned. You can extend the content type to include any metadata you need allowing you to have different sets of metadata for the same file in different locations.


4

In 2013 (but not in 2010 as you say) you can nest Document Sets. So then the only differences is the fancy WelcomePage and the possibility to add Shared Metadata between the document set it self and all contained files. And as you write, the fact that you do not have version history on folders, but on Document Sets. More about document sets from TechNet ...


3

It looks like folders aren't offically supported by Microsoft within Document Sets. See the Document Sets planning (SharePoint Server 2010) From the document: Folders are not allowed in document sets, and metadata navigation cannot be used in a Document Set There may be an unsupported way, but it will likely cause problems.


3

I'm not sure if I'm answering the right question, but I used this method to check if Doc Set (folder) exists, and if not, create: [Microsoft.SharePoint.SPFolder]$targetFolder = $rootWeb.GetFolder($targetDocLib.RootFolder.ServerRelativeUrl + "/$docSetName") if (-not $targetFolder.Exists) { # create } This approach worked for me.


3

Here you have something quite similar (just few changes needed): How to Display a SharePoint Dialog from Ribbon Button and Get Selected Item Context Basically you need two things: Custom ribbon/button similar to one described in article. With usage of dialog framework you open custom page and pass selected items values as querystring (all described in ...


3

First off its not available in SharePoint Foundation, so you need the full SharePoint 2010 Server. Here it can be enabled at site collection level. The feature is called Document Sets. When enabled you can add a document set content type to your list, giving you the ability to create document sets from the "new document" button in the ribbon.


3

If the desired view is consistent across the Document Sets, you can configure it once when configuring your Document Set content type and all new instances of this Document Set will reflect this. The settings you're looking for are referred to as the "Welcome Page" settings. See: Create and configure a new Document Set content type Under the heading ...


3

My suggestion (explained at the bottom) is to just not use folders, then showing only specific groups of items in one view becomes quite easy. Alternatively you could use folder specific default metadata values, then filter your list view on those... otherwise you will probably need to install SPD or create a list view from scratch using HTML and JavaScript ...


3

You could probably tweak the library view to achieve this scenario. 1) Go to the library and click on create view in the ribbon. Click on 'All Documents View' under 'Start from Existing View' 2) Under 'Filter' Section set the following query using the drop downs Content Type = "Folder" AND Name = "Folder 1" OR Content Type != "Folder" 3) Create a ...


3

Most probably the specified error occurs since you are trying to get site-level Content Type while web is not a root web. Quick fix Replace the line: var docsetContentType = web.get_contentTypes().getById(docSetContentTypeID); with: var docsetContentType = ctx.get_site().get_rootWeb().get_contentTypes().getById(docSetContentTypeID); How to ...


2

Great question. You may want to consider creating an event receiver that is triggered whenever an item is created. If the content-type is folder then delete it.


2

My guess would be that as the DocumentSet object derives from SPFolder, you should use the same method to rename a folder than a document set so something like set.Item[SPBuiltInFieldId.Title] = newDsName; set.Item.Update(); //or SystemUpdate(false) or you could use the MoveTo Method on the SPFolder Object


2

Yep you can. You need to make sure that you have the Document Set feature enabled on the Site Collection and then from the Content Organizer Rules you can specify the Group as 'Document Set Content Types' and the type as 'Document Set'. One thing people frequently forget is that you also need to have the content type available within the destination ...


2

I know this really should not be an answer, and should be a comment on the accepted answer, but apparently I cannot add a comment. In any case, I have a potential solution to the problem of the Inherits attribute, and needing to set it to True so you can publish content types correctly vs. needing to set it to False so that you can preserve your declarative ...


2

An example of using a document set would be for something like a RFP for a potential client. There might be a Powerpoint Presentation, a Sales Document, and some Marketing material. These can be rolled into a document set content type so that each new RFP contains these 3 files. It helps organize process where multiple types of content define the ...


2

Create a workflow that fires on the addition of a document set, and creates the default documents in the current document set.


2

You need to keep in mind that Document Sets are just folders on steroids. I tried to make HashTable approach to work without any luck. But this code will do the job: using (var site = new SPSite("http://myultracooltestsite")) { using (var web = site.OpenWeb()) { SPList list = web.Lists["MyCoolDocLib"]; DocumentSet ds = ...


2

The shared fields are set by an itemeventreceiver, so won't be filled till the document is actually added and saved to the document set.


2

Unfortunately there is no standard SharePoint Designer Action to copy/move a document into a document set. The only similar action is to copy the list item which could copy it from one list to another. Seems like you will have to create your own SharePoint Designer Activity which allows you to move/copy a file to a document set - keep in mind that a ...


2

Here's an idea. Navigate to the Document Set library Go to the Library tab in the Library Tools section at the top of the page. Click "Open with Explorer" Rightclick the Document Set you want to view the size of and click "Properties" The size of the folder will show the size of the document set with all of it's contents.


2

In the settings for a Document Set you can choose what View to use. When you click on a Document Set content type in library settings, one of the options is "Document Set settings". The last option in this dialogue allows you to select a defined view on the library that will be used to show the contents of that Document Set.


2

public static SPFile CopyFile(SPWeb web, string sourceUrl, DocumentSet docSet) { SPFile file = web.GetFile(sourceUrl); string destinationFolderUrl = docSet.Folder.Url; destinationFolderUrl = (!destinationFolderUrl.EndsWith("/")) ? destinationFolderUrl + "/" : destinationFolderUrl; file.CopyTo(destinationFolderUrl + file.Name, true); web.Update(); ...



Only top voted, non community-wiki answers of a minimum length are eligible