Google Sheets Pivot Tables: Grouped Summaries, Access, and Alternatives (2026)
Grouping is the part of a pivot table that turns raw rows into a summary someone can read. Until this week, Google Sheets threw that work away more often than most people realised.
On August 25, 2026, Google shipped grouped field persistence for pivot tables in Google Sheets. The change is small in the release notes and large in practice.
This guide covers what shipped, who has it, and what the announcement leaves unsaid. It also covers what to do when the deliverable you owe is a report rather than a pivot table.
What Google shipped on August 25, 2026
The Google Workspace Updates blog describes the change in one line. Google Sheets "now supports grouped field persistence for pivot tables."
Two behaviours changed together. Custom groupings now survive being removed from the layout, and they now survive a file round trip with Microsoft Excel.
| Before | After | |
|---|---|---|
| Remove a grouped field from the layout | Configuration lost | Retained as a reusable source field |
| Import an .xlsx pivot table with grouped fields | Groupings dropped from the field list | Groupings preserved |
| Export back to .xlsx | — | Grouped field configurations preserved |
| Admin control | — | None; the feature has no admin toggle |
What a grouped field actually is
A pivot table starts from columns in your sheet. A grouped field is a column you have bucketed into something coarser.
Dates are the common case. A single order date column becomes months, quarters, or years, and the summary suddenly fits on one screen.
Numbers work the same way. Order values become bands, and ages become brackets, so the reader sees shape instead of noise.
Custom groupings are the third case. You hand-pick which categories belong together, which is how regions, product families, and account tiers usually get built.
The Excel interoperability fix is the real news
Google states the old behaviour plainly. Import an .xlsx file whose pivot tables use grouped fields, and "those custom groupings were dropped from the field list, requiring manual recreation."
Read that quote carefully. The groupings did not silently break, and they did not partially survive. They disappeared from the field list entirely.
Anyone who has inherited a workbook knows the cost. You open the file, the numbers look plausible, and the buckets someone spent an hour defining are simply gone.
Google now says grouped field configurations "are accurately preserved when importing/exporting spreadsheet files." That makes Sheets a safer destination for a workbook you did not build.
Microsoft's own guidance explains why the Excel side matters. Its documentation on creating a PivotTable notes that your data "should be organized in columns with a single header row." Microsoft also documents grouping and ungrouping data in a PivotTable as a first-class feature, which is exactly what used to be lost on import.
Availability and rollout
The rollout is staged, and the two release tracks are weeks apart.
| Track | Start | Note |
|---|---|---|
| Rapid Release domains | August 25, 2026 | Gradual rollout, up to 15 days for feature visibility |
| Scheduled Release domains | September 14, 2026 | Gradual rollout, up to 15 days for feature visibility |
Access is unusually broad. Google lists it as available to "all Google Workspace customers and users with personal Google accounts."
Administrators have nothing to configure. Google states directly that "There is no admin control for this feature."
What the announcement does not say
Three gaps are worth naming, because filling them with guesses is how teams get burned.
No stated limit on how many grouped fields persist. The post describes the behaviour and does not publish a cap.
No detail on partial or conflicting groupings. An imported workbook where two groupings overlap is not addressed.
No statement about Apps Script or the Sheets API. Whether scripted pivot definitions see the retained fields is not covered.
How to use a grouped field in a summary
The workflow is short once the groupings stick.
Open the pivot editor and look at the source field list in the sidebar. Grouped fields now sit there as reusable entries rather than living only inside the current layout.
Drag one into Rows, then unassign it when you want a different cut. The configuration stays available, so re-adding it costs a click instead of a rebuild.
Keep one habit from the Excel world. Confirm the source range still has a single header row before you trust any grouping you did not create.
Alternatives when the deliverable is a report
A pivot table is a working surface, not usually the thing you send. The gap between the two is where most of the time goes.
Three paths are common. You can keep the pivot table and screenshot it, or rebuild the same cuts as charts. The third path is to hand the file to an agent and ask for the finished artifact.
Powerdrill Bloom sits in that third category. You upload the export and describe the grouping and the output in natural language. What comes back is a chart, a written report, or slides built from the same run.
The relevant contrast is scope rather than quality. A pivot table answers a question inside a spreadsheet, while a report has to survive being forwarded to someone who never opens the file.
Our guide on summarising Excel data without pivot tables walks the same ground from the Excel side. For the Sheets side, see turning Google Sheets data into charts and our explainer on Google Sheets canvas.
If you are shopping rather than building, our roundup of AI tools for Google Sheets analysis covers the category.
Conclusion
Grouped field persistence is a small feature with an outsized effect on inherited workbooks. The honest headline is not "Sheets got better at pivot tables" but "Sheets stopped discarding work that Excel had already done."
Two things follow. Importing an .xlsx pivot table is now a much lower-risk move, and rebuilding buckets by hand should become rare.
If the buckets were only ever a step toward a document, skip the rebuild entirely. Start on the free tier, compare plans on the pricing page, and try Powerdrill Bloom on the export you were actually sent. See also the AI canvas and Excel AI assistant pages.
Frequently asked questions
What exactly is a grouped field in Google Sheets?
A grouped field is a source column you have bucketed into something coarser, such as dates rolled into months or numbers rolled into bands. Custom groupings, where you hand-pick the members, count as well.
Do I need an administrator to turn this on?
No. Google states there is no admin control for this feature, and existing generative AI and Workspace settings are unaffected by it.
When will I actually see it?
Rapid Release domains started on August 25, 2026, and Scheduled Release domains start on September 14, 2026. Both are gradual rollouts, with up to 15 days for the feature to become visible.
Does this work for personal Google accounts?
Yes. Google lists availability as all Google Workspace customers and users with personal Google accounts.
Will my Excel groupings survive a round trip now?
Google says grouped field configurations are accurately preserved when importing and exporting spreadsheet files. The announcement does not publish limits, so verify a copy of any workbook that matters before you rely on it.