Forum Discussion
SPO list view not showing filtered/grouped by items in Chrome/Edge
Hi, I'm troubleshooting an issue in one of our long-time used SP list (around 3000 items). For an unknown reason, the view (which is Filtered by the people/group type column using the [Me] and t...
- I reported it to Microsoft this morning. But I may have found a workaround. Try this on your SPO and let me know if it works for you.
Create your view as normal but just put the [Me] filter on it. You should have results still. Now while viewing your results click on a column header dropdown and choose to Group By from there. On my end the results seem to stay. Then you can save the view as another view. For me this seems to work. I can even see the Group By clause when I edit the new view normally. It's strange.
I am having this same exact issue and came to this forum for a solution. I wasn't aware of the cookies and deleting the sharepoint.com cookies in Chrome does work until I refresh the view again. But in Edge it doesn't seem to work when deleting the cookies and refresh. Still blank.
gsreddin Have you reported this to MS Support? Any resolution?
I'm still confused about what the actual issue is, if a device, a browser, a cookie, the list filtering, and grouping?
- I reported it to Microsoft this morning. But I may have found a workaround. Try this on your SPO and let me know if it works for you.
Create your view as normal but just put the [Me] filter on it. You should have results still. Now while viewing your results click on a column header dropdown and choose to Group By from there. On my end the results seem to stay. Then you can save the view as another view. For me this seems to work. I can even see the Group By clause when I edit the new view normally. It's strange.gsreddin Hi, your workaround works really great, thank you for that! However, once I need to set the view to show the groups collapsed by default, I have to edit the view, save the view and then the view starts failing again and not showing any items when refreshed.
This should be really addressed and fixed by MS. However, I'm tired of troubleshooting this for now and decided to live with your workaround.
