As mentioned by Marc01350 and florianwachter, this feature is not good news.
This will significantly confuse end-User people as well as upset a lot of Application Designers and Developers across a range of disciplines. Here are just a few reasons why I see this a being a massive backward step:-
- Imagine where a filtered View only displayed a list of 20 or so documents, and then a user clicks on ‘Clear Filters’ and they get presented with 2,000! How does that make it ‘easier’ for end-users to find the document they want to refer to or look at?
- Where the AssignedTo = [Me] approach can be ‘broken’ and I can see what other people are responsible for.
- A ‘Status’ field as a filter shows only ‘Live’ documents and but with ‘Clear Filters’ clicked you can see ‘Draft’, 'Work in Progress’, ‘Out of Date’ etc and all in no particular order!
- A date and time dependent View with a ‘Today’ filter then shows all documents regardless.
A good way of considering some of the implications is to consider this in relation to common applications. Just think what happens with some of the data prepared through commonly used Power Apps! What changes when users can ‘see’ all documents within your Expense Approval system / Vacation requests / Incident management / Support desk tickets / Onboarding process etc etc.
This is a seemingly simple feature which has massive adverse implications and where the bigger picture was most definitely not thought about when being considered for inclusion.