Forum Discussion
MicrosoftUpdate: Document Sets in Modern Document Libraries
ZdenkaCechMavenir Thanks for the details (and example) for the icon issue! I've only seen the folder icon when the item was originally created as a folder and later changed to a document set. Would you be willing to answer a few questions to help us understand the circumstances where the wrong icon is shown?
Do the document sets which have generic folder icons have the correct content type (e.g. "Document Set", not "Folder")? You can check this in the details pane. If the content type is "Folder", does changing that to the expected document set type restore the correct icon?
When you click a document set which has a folder icon (to navigate into the folder), does the details pane automatically open if it wasn't open before?
Might someone be using a tool to sync the contents of that library? It's possible that some applications accidentally overwrite the properties which distinguish document sets from generic folders.
Thanks,
Michael
1. I can confirm it is Dset not folder ct
2. yes, it opens automatically the details pane
3. the ds was created by powershell scripts using the command:
[Microsoft.SharePoint.Client.DocumentSet.DocumentSet]::Create($spoCtx,$sRootFolder,$sDocumentSetName,$ct.id), later I run another script to create a subfolder within the dc.
Maybe could be a Sharegate we run it to copy some files in there and one time to check broken inheritance on the items and restore them back. so maybe sharegate. I can run a test. if it is ShareGate I'll report it to them. Would you have a powershell command to check its icon property and maybe change it too? Thanks *Z
Further to my own posting, this issue appears to be isolate to IE, and when structural nav is used.
One of my sites has updated to the modern experience for document sets, but my Current Navigation pane does not display anything in the modern view when displaying the contents of a document set, just an empty panel - changing back to classic the nav appears (Structural Navigation). Makes it unusable at the moment.
ZdenkaCechMavenir Thanks for confirming the content-type! If you can get the ListItem corresponding to the document set with the folder icon, you can do something like this:
$listItem.Properties["vti_progid"] = "SharePoint.DocumentSet"
$listItem.Update()
I’ve experienced a similar issue when using ShareGate to migrate from a file share.
In ShareGate I set the mapping from folder (fileshare) to document set (SharePoint). For the most part the mapping works, but occasionally some fileshare folders migrate to a folder content type in SharePoint.
I’ve noticed the frequency of this issue has reduced with recent ShareGate updates, but it still occurs and seems random.
Seems like a ShareGate issue.
