Allowing identical names in Document library with Document Sets
Afternoon team, Hope you're all well. Let me run something by you, I'm after some thoughts on my scenario. I have a document library, which I've configured with a single Content Type. A document set, with associated columns and documents. In testing, we've hit the age old problem of duplicate names not being allowed. As I understand it, this occurs as the Doc Set is a child of the folder type,, which means the initial value provided to the Doc Set is used to construct the subsequent URL. Duplicates are barred for obvious reasons. I have a scenario where duplicates within the name field are desired. As this is a problem on DocSetCreation, all I can think of as a possible solution is the Document ID Site Collection Feature. I'll be testing this but am curious as to how other community members have gotten around this problem. Cheers Steve
Content type created but not finding in file properties content type dropdown - SharePoint 2019
I'm in SharePoint 2019 On-Premise, and I've created a site content type. Added it to list form settings. However, I can't locate it in the file properties dropdown. The other existing content types display correctly within the document properties, but the recently created one only appears only at the document set folder level. My goal is to have it included in the file content type dropdown. Can someone provide assistance?Icon of Document Sets changed to default folder icon - Support claims it is "by design"
Some of our customers heavily rely on the Document Set functionality. Last week we noticed that the icon of Document Set has changed within a list view from to This seems somehow to be related to the new functionality to change the colour of the folder. All tenants which already received this new feature show the wrong icon for Document Sets. All other locations ("New" menu, Details pane) are still using the Doc Set icon, so the list view seems the only place where the icon has changed for a Doc Set. I had a call with MS support today, and they told me (like on many SP-related issues before) that this is "by design". I am using Document Sets since 2010 - claiming that it is "by design" to change the Doc Set icon to the folder icon is like changing the icon of a Word file to the generic file icon.
How to have the Document Set ID embedded into your word templates as a property to select from
Hello I am creating a QMS, and have built templates where the document ID and document title automatically populate upon creation. Each quality document will have a native Word & PDF file associated with it, currently, sharepoint generates two different IDs which means when the PDF is uploaded the ID does not match what is stated in the document. To overcome this, I have created Document Sets, so that the native doc & PDF can be placed under them and I want to use the Document Set ID as the overarching Document Number stated on the document. In the Word templates, I am unable to select Document Set ID in the drop-down, does anyone know a way to do this? I attempted to create a look-up column so the documents have the Document Set ID within their properties, however, cannot get it to populate correctly. Does anyone have steps to create this successfully?"Move to" within the same library breaks document sets
I just had another call with Microsoft Support and it seems that they just don't get the issue. Try the following: 1. Activate document sets site collection feature 2. Add document set content type to a library 3. Create a document set 4. Show the ID column in the list view 5. Add some folders or files to the document set 6. Use the "Move To" function (not drag & drop!) to move the document set to a new location within THE SAME LIBRARY! What basically happens is, that it is not an actual move but a copy and delete of the document set. This leads to the point, that the following things are broken after the "Move to" of the doc set: - Unique permissions & sharing links on the document set or files/folders within the set are broken (Move To doesn't move permissions, so every item within the doc set gets reset to inherit permissions) - Document set captured versions are broken (the links to the file versions) - Lookups to the document set are broken - Durable links are broken - When using the Document ID service -> The links are broken too When using drag & drop to move the file to a new folder -> everything is fine. This also only occurs on document sets. When using "Move to" on normal folders, the folders gets moved as expected and doesn't copy & delete. I am a bit frustrated about this because Microsoft Support just keeps telling me that this is by design. That might be true when moving the document set to another library or site. But moving within the same library, it can't be by design that drag & drop behaves differently as "Move to". Or that moving documents sets with "Move to" behaves differently as "Move to" on folders. Is there anybody else faces this issue or are document sets such an exotic feature, that we are the only ones who struggling with this?Add columns to new Document Set form
I created a document library with multiple columns and added a Document Set as a content type to the page. However, when users create a new document set, they only have the Name column on the NewDocSet.aspx page. How can I add more columns to this page? I want my end users to enter the column data here and not have to go back in to fill out the column.
Documents from Document Sets open in Read-Only
Hello, I read a couple of older posts that reference files opening as read-only from document sets with metadata attached. In the document set I've got a new entry form where the user inputs their data and then uploads their files as desired after the folder is created. I've got the same issue even when check-in/check-out is disabled. Is there a work around for this issue now? I ask because we want to work in the desktop client app (Excel, Word, etc.) Thanks
