-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document Sets are intermittently treated as "files" #57
Comments
After further investigating with the client, this might be correlated to disabling the folder option (in some guides, they recommend this). With this said, is there a way to query inside of docsets using this filepicker without changing this setting? This is still a pending issue |
After reproing this without the sdk itself (which appears to be a link builder at the end of the day), we opened a ticket with Microsoft. The ticket has still not been triaged and for the time being we wrote our own (less featured) file picker using the graph API. Hope to use this library again soon but for the time being, we are unable to use this with specific clients due to bugs on the file picker side. |
Hey @nicolasiscoding , I'm going through and looking at some of the older issues. Sorry this was never looked at. Did anyone ever address it outside of this thread? If not, I can try to take a look. Thanks! |
Hi @JCrew0 , it hasn't been addressed and it's currently wading in a Microsoft support queue somewhere. We still aren't sure what's causing this because when we wrote our own file picker, the graph APIs are returning the file types as expected. It's something local to the tenant with respect to the file picker post redirect. |
Describe the bug
When reproducing a user's scenario on a screenshare, their Document Set is being seen as a file (can not click into it) and not a folder with a collection of documents.
When performing this in my personal SharePoint environment, the Document Set is treated as a folder and works fine.
When performing the network trace on the user's screens are and looking at the decoded URL (and prettified for debugging)
URL:
Query Parameters ( decoded & beautified):
I also noticed that the document set has a custom content type whereas mine does not.
Is there a reason why in my tenant I can click through the Document Set, but in theirs I can not? Could it be a scopes/permissions issue? Or the custom content type against my filters?
The text was updated successfully, but these errors were encountered: