Had to write a PowerShell script to go through a bunch a lists across different sites to enable Metadata Navigation and Filtering and include some Key Filters.
This issue is similar to the problem reported at https://social.technet.microsoft.com/Forums/office/en-US/50001a2f-bf80-44fb-b8c9-4835cc15b7f6/problem-with-metadata-navigation-key-filters-and-grouped-views.
The error happens when you’ve enabled the Metadata Navigation and Filtering feature, and configured a list with Metadata filters, and has a list view that is grouped by a column:
- If the Group By is set to Collapsed by default, then when you apply a Metadata Filter and expand a group, it brings back all items instead of filtered results.
- If the Group By is set to Expanded, applying a Metadata Filter works fine, until you go to the next page, and again all items are returned instead of filtered results.
While Microsoft released a fix for this in the SharePoint 2013 July 2014 CU, it seems that there is still 1 edge case where this error is happening:
- The Group By column you’re using is a Lookup field
As of March 2017, it seems to be happening in SharePoint Online as well.
The Content and Structure page in SharePoint (aka Site Manager) has useful reports that allow you query for items in your site collection, such as the Checked Out To Me report that brings back a list of all documents currently checked out to the user.
All the reports run recursively, meaning it brings back results from your currently selected site and all its sub sites and lists/libraries.
However, one of the most common issues around is that the report is not bringing back results recursively from its child locations, or it used to do it but has suddenly stopped. And the only way to get the results is going into the same level at which the items are at (in the list/library itself, or even in the folder the item is in) to be able to show up in the report. Not as useful anymore…
Why does this happen?