Multiple default views not working

[Villads Chester]

Using Sharepoint online I am trying to setup several different defaults views - fx. one for Top-level document library and another for files in folders.

I am applying both Top-level view, folder view and using content-type.

However, it seems like I cannot get both Folder and Top-level view to work - the system automatically applies same view to both. Any idea if that is no longer supported or why?

I was using this guide as input for Folder and Top-level views: http://www.cyberviva.com/sharepoint/different-type-of-view-in-sharepoint-document-library-root-sub-f...

[#2]

We have same issue. Everything works fine in Classic experience. Changing to Modern will not switch views from top level to inside a folder view and back. In Library settings both views showing as default view.

[#3]

@Villads Chester 

yes we have exact the same issue.
Do you know, if there will be an update soon?

[#4]

Unfortunately not, @lotz-hellerau 

[#5]

@Villads Chester 

Hi,

I have followed a similar guide to configure Content types and views for different folder levels, but nothing works as expected.

Any updates on this issuse?

Thanks in advance

---

[#6]

@Deleted 
No unfortunately I did not find some news about it. This is really really bad.
Does anybody has an idea why microsoft do not care about that issue?
Maybe there are some other workarounds to do these things?
I'm afraid that dokument set content type does not work in SharePoint Lists, because there the view is switching. 

For now I helped me by formatting the name column of the relevant list. Now when users klick the name column the view is changing to the view I specified. But this is not very handy!
We really need some update :)

[#7]

Same here. Same issue. Why they would remove this issue is beyond me. There are a lot of uses for it. Can't see what it harms.

[#8]

I am also experiencing the same issue. The defaults work correctly in the classic experience, but not in modern. Defaults set for Document Sets do work correctly, but not for any other content type.

[#9]

I see that the last comment on this was a couple of months ago but I'd just like to chime in that we're experiencing the same behavior.  We've got a library with a top level view of All Documents and then within the top level folder there are sub-folders that are assigned to different default views. 

I used the example outlined in this link - https://camerondwyer.com/2014/01/06/harness-sharepoint-default-views-at-different-navigation-hierarc...

As others have pointed out, this works well in Classic View, the issue is that we are using Modern View.

I hope find a solution by continuing to search, but for now the issue persists.

[#10]

@jbryant

The same for me, stil no solution for Modern Site 

[#11]

End of Jun 2020 - still an issue for modern experience

[#12]

Same issue here. Did not find a solution yet either.

[#13]

We're having the same issue. It's incredibly annoying because we would like to use different views depending on where you are in the library but this is not possible. The only solution I've found is to make new document libraries but that has the problem with not being able to redirect Teams channels file locations to these new document libraries. It's really idiotic that MS does not fix this. It worked before, why does it not work now...

[#14]

@Villads Chester I have exactly the same problem. In my case I have a single top level view for my Document Set Folder and want to have multiple views inside the folder when looking at the files. Using the Document Set Web Part it does show that I have the views available to select however when selecting the folder it opens up the folder and displays the contents (files) of the folder in the same view as the folder. It doesn't change the view from the folder view to the view I have listed as the default view for files and yet it still displays the files. I am stuck. So for now I am just going to stay with the Web Part Document Set Content and forget about the views for now. Kinda sucks really.

[#15]

It's 2021 and this issue is still live. It seems Microsoft doesn't care much about these crucial feature requests.