Forum Discussion
MicrosoftUpdate: Document Sets in Modern Document Libraries
This is very cool and we're slowly testing this in our production environment.
I found of the limit today; you can't MOVE TO or COPY TO a document set to another location...for now. Hopefully they will add this feature soon!
Sebastien Gagne LincolnDeMaris
The MoveTO and CopyTO buttons are still not working properly, even though Lincoln stated this was "near the top of the roadmap activities". But currently a document set can only be moved/copied to another document SET instead of a library.
If a target library is configured to accept the same Document Set Content Types, it should be available as a target library for MoveTO/CopyTO. Basically a no-brainer, as the existing MoveTo/CopyTo don't make sense at all.
LincolnDeMaris could you please provide a status update? Or somebody else from the MS product team?
JanKlooster , One way I found to move document set between librairies is to create a folder into the source library, move the document sets into the folder. Then you can move the folder into another library (document set content type needs to be available) and then you can move the documents sets inside the folder at the root of the library.
UPDATE: I found however that the document set metadata does not get transfered. It sets back to folder (even if we see the document set icon). Need to set the content type back to document set and fill the metadata.
Martin-Coupal I'm having the same problem with moving sets around to other libraries. No metadata transfer.
I would also want an update on it. I would love to see Move to/Copy to another library with document sets enabled. Currently I use MS Flow to achieve that via _api/SP.MoveCopyUtil.MoveFolder REST service.
