Can't Rename DocumentSet

Question

Collection admin on SharePoint 2016 on premise. Tried renaming DocumentSet in UI - it lets you enter info and save but nothing changes. Used the WebDav UNC to do the rename via file explorer and get error message that the file name is not valid.....even if I just add 1 character or remove one character. I am able to rename the DocumentSet using SharePoint Designer.

Any help/input would be appreciated.

Answer 1

Hi @Lee Seidel
I'm glad to hear you solve the problem, if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others.". and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

Issue Symptom:
Collection admin on SharePoint 2016 on premise. Tried renaming DocumentSet in UI - it lets you enter info and save but nothing changes. Used the WebDav UNC to do the rename via file explorer and get error message that the file name is not valid.....even if I just add 1 character or remove one character. I am able to rename the DocumentSet using SharePoint Designer.-

Current status:
I found a workaround for the user which leads me to think it has something to do with how the web ui calls to make the rename and may be related to the large number of files within each docset that must be renamed as the option to prefix the file name with the docset name is set to on.

Switching the view to quick edit allows the folder to be renamed without issue. I think the rename in quick edit is similar to call made when in SPD vs. what is done in the standard UI rename/property update.

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi @Lee Seidel
You could check whether there is any other document set with this problem. You could also check if there is someone else opening the files in this document set, we will also be unable to rename it: https://prairiedeveloper.com/2015/11/unable-to-rename-sharepoint-folder/

What's more, you could set file size column visible in list view to check whether there are some files with 0 KB in the document set, if yes, try to remove them to see whether this problem persists.

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Thanks... No 0 byte files. No other files open.

I found a workaround for the user which leads me to think it has something to do with how the web ui calls to make the rename and may be related to the large number of files within each docset that must be renamed as the option to prefix the file name with the docset name is set to on.

Switching the view to quick edit allows the folder to be renamed without issue. I think the rename in quick edit is similar to call made when in SPD vs. what is done in the standard UI rename/property update.

So no idea of what is causing it..... but..... I did find a solution for the customer that they are fine and happy with. :-)

Thanks for taking the time to provide your feedback. It was appreciated.