A few weeks ago I needed to create document sets but having done this a couple of years ago I approached with trepidation remembering that following most documentation was like knitting with spaghetti. Fortunately, as a long time subscriber, I found your explanation and, although a long process, it was by far the clearest and easiest to follow. I appreciate your work Greg.
This is a great overview, thank you. The main issue when using anything other than folders is getting users to actually tag their documents appropriately. We have used metadata defaults at times, but even marking metadata as mandatory still doesn't force them to tag, it just shows the files as 'needing attention'. Is there anyway to actually stop users saving/creating/copying a new document in Sharepoint until they have tagged it? Otherwise, how do you ensure you don't end up with a huge bucket of un-tagged files?
Document Set has very many advantages, but I see one problem - with some inattentive users :( How to block accidental drag and drop / moving one "Document set" to another next to it ? I can't find how to block this for users who must have add and edit rights - no delete rights. Anyone know how to block this possibility ? For folders, it's easy - because the lack of deletion rights blocks such drag and drop. For Document Sets - I don't know how to block
@@SharePointMavenWell... It's not a permission issue I think. I tested it on another library - tested user have a permissions to edit and add (no deletion) in library. For folders drag drop / move is impossible - behavior OK - message about impossibility. For a set of documents - Dragging is possible - the content is copied to another set of documents - I don't want that. In this target document library I want to operate only on a set of documents - folders are disabled. But this behavior It destroys my idea of a solution.
A few weeks ago I needed to create document sets but having done this a couple of years ago I approached with trepidation remembering that following most documentation was like knitting with spaghetti. Fortunately, as a long time subscriber, I found your explanation and, although a long process, it was by far the clearest and easiest to follow. I appreciate your work Greg.
My pleasure and thanks for the kind words🙏🙏🙏🙏
Love your content. Straight to the point and very useful.
Thank you - appreciate kind words!
Excellent video Thanks very much Greg !!
My pleasure, thanks for feedback!
Great explanation Greg. Thank you.
You are welcome. Thanks for the feedback.
Great Content! As always ❤
Appreciate it! Thanks for the kind words.
This is a great overview, thank you. The main issue when using anything other than folders is getting users to actually tag their documents appropriately. We have used metadata defaults at times, but even marking metadata as mandatory still doesn't force them to tag, it just shows the files as 'needing attention'. Is there anyway to actually stop users saving/creating/copying a new document in Sharepoint until they have tagged it? Otherwise, how do you ensure you don't end up with a huge bucket of un-tagged files?
There is no way to enforce tagging: sharepointmaven.com/how-to-make-sharepoint-metadata-columns-required/ It is more of a soft warning.
So you would only recommend document sets for small projects. What do you recommend for a mix of small and large projects?
Sites and Doc Sets
Can you create a video on the Document Approval workflow?
Already have one: th-cam.com/video/DX-plm8E0hM/w-d-xo.htmlsi=LvSb5QhnXoh_235-
@@SharePointMaven thanks
Document Set has very many advantages, but I see one problem - with some inattentive users :(
How to block accidental drag and drop / moving one "Document set" to another next to it ? I can't find how to block this for users who must have add and edit rights - no delete rights.
Anyone know how to block this possibility ?
For folders, it's easy - because the lack of deletion rights blocks such drag and drop.
For Document Sets - I don't know how to block
Hmm, what do you mean moving doc sets next to each other?
@@SharePointMaven “accidentally” doing a drag and drop to a neighboring document sets.
The contents are copied
@@BartekWojtal Oh OK. But Doc Set is also like a folder - can't you assign same custom permission level to them as well?
@@SharePointMavenWell... It's not a permission issue I think.
I tested it on another library - tested user have a permissions to edit and add (no deletion) in library.
For folders drag drop / move is impossible - behavior OK - message about impossibility.
For a set of documents - Dragging is possible - the content is copied to another set of documents - I don't want that.
In this target document library I want to operate only on a set of documents - folders are disabled. But this behavior It destroys my idea of a solution.
How does it show up in file explorer?
Without metadata