SharePoint list view with 2 grouping levels not working

DB365-3161 136 Reputation points
2026-07-13T11:50:51.2233333+00:00

Good day.

I have a SharePoint list with less than 3000 items. The list has a view with 2 grouping levels. The view worked 100% until today.

TL;DR: it seems like 2 grouping levels no longer work in SharePoint list views. This looks like a bug/regression.

Details:

The original view has 2 grouping levels:

  • Group 1 = indexed lookup column to list with < 800 items.
  • Group 2 = indexed lookup column to library with > 5000 items.

The groups are collapsed by default.

This view worked 100% until today (2026/07/13).

Current behaviour:

  • When expanding the first group level, nothing happens.
  • When clicking on one of the item's first group level (i.e. effectively filtering the view by the first group level's value), the view is blank ("We didn't find anything to show here").

Troubleshooting:

  • I've edited the view to set the groups to be expanded by default. This results in grouping by the first group only, and the view otherwise works as expected.
  • I've removed the second grouping from the view, with the groups collapsed by default. This view works as expected.
  • I created a test view with 2 groupings: both groupings are by text columns "native" to the list (i.e. not lookup columns). This has the same unexpected behavior as the original view.
  • Tested in Chrome and Edge on Windows 11.

My conclusion:

  • 2-level groupings are no longer working in SharePoint views.
  • This is either a bug/regression, or this is by design, but the view editor still allows 2 groupings.

Please test this and confirm whether this is a bug, or whether MS is removing support for 2-level groupings in list views.

Thank you.

Microsoft 365 and Office | SharePoint | For business | Windows

Answer accepted by question author
Rin-L 23,385 Reputation points Microsoft External Staff Moderator
2026-07-14T07:09:06.8333333+00:00

Dear @DB365-3161 and other community members experiencing the same issue, I would like to share an additional last updated at July 13, 2026, 11:56 PM (GMT+7):

User's image

According to the latest update from Microsoft, the fix has been validated and is working as expected. This is certainly a positive sign, and I hope the deployment will continue progressing smoothly.

Thank you all for following along with the updates I've shared throughout this discussion!

Was this answer helpful?

6 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Rin-L 23,385 Reputation points Microsoft External Staff Moderator
    2026-07-13T12:20:31.0766667+00:00

    Hi @DB365-3161,

    Thank you for taking the time to share such a detailed description of what you’re experiencing.

    Based on what you’ve described, I’d like to reassure you that the issue is not coming from your side. This has been identified as a service-related incident on Microsoft’s end, and the team is actively working on it.

    To give you a clearer picture, here’s a concise update on the situation:

    Some users' document libraries and list views using multiple group filters may not display results in SharePoint Online

    Last updated at 2026-07-13 6:26 PM (+07)

    • Summary of Impact: Some SharePoint Online users experienced issues where document libraries and list views configured with multiple group filters (using both Primary and Secondary grouping) did not display full or expected results, and in some cases may not have displayed results at all. The issue affected the rendering of grouped views, impacting users’ ability to reliably view and work with items in affected document libraries and lists. Impact was limited to specific views using multiple group filters; other views and core SharePoint Online functionality continued to operate as expected while the issue was under investigation.
    • Impact Time: Start: Monday, July 13, 2026, at 06:42 UTC. End: Not yet resolved (incident remains active as of the latest update).
    • Scope of Impact: The issue affects some users in the organization who attempt to view SharePoint Online document libraries and list views that use multiple group filters, specifically those configured with both Primary and Secondary grouping. In these affected views, users may see incomplete data sets or no results, even though items exist in the library or list. The impact is limited to grouped views and does not apply to all SharePoint Online users or all document libraries and lists.
    • Action Taken: Engineering is investigating the issue within SharePoint Online. They initially analyzed network logs to validate a suspected regression in the document libraries codebase. After further investigation, they identified a recent change to the service component responsible for rendering grouped views as the source of impact. A fix has been developed and is undergoing validation to ensure it resolves the issue without introducing additional risk. The team is also determining the safest deployment approach for rolling out this fix to affected environments.
    • Contributing Factors: A recent change to the SharePoint Online service component that handles rendering of grouped views in document libraries and lists introduced a regression. This regression affects views that use multiple group filters, specifically those configured with both Primary and Secondary grouping, causing them to fail to display full or expected results and, in some cases, any results at all. The faulty change in the grouped view rendering logic is the direct cause of the observed impact. 
    • Next Steps: Engineering will complete validation of the developed fix to confirm it fully resolves the grouped view rendering issue without side effects. They will then determine and execute the safest deployment strategy to roll out the fix across affected SharePoint Online environments. Further updates will be provided as the deployment plan is finalized and implemented, with the next scheduled update by Monday, July 13, 2026, at 5:00 PM UTC, or earlier if significant progress occurs.

    Just to add a bit of context, as a forum moderator, I’m not part of the internal engineering team and don’t directly work on the fix. However, I do my best to keep you updated on the current situation and share the latest available information, so you and others experiencing the same issue can clearly understand what’s going on without feeling worried or having to spend extra time troubleshooting.

    I hope this information can be communicated more broadly so that all affected users are aware of the situation. I also hope the issue will be resolved soon, allowing everyone to enjoy the best possible experience again.

    Thank you again for your patience and understanding.


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?

    8 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.