Contact

Google Sheets web app (rolling service) · Data preparation and inputs · Intermediate

Group Google Sheets table records and check category totals

Use a Google Sheets table group-by view to inspect stock requests by category, reconcile counts and sums, and check a changed record.

Documentation-reviewed candidate; native application verification not performed. · Editorial standards

Quick answer

A table group-by view keeps related records together and can display category-level calculations. Use it to inspect the records behind a subtotal, rather than creating a separate pivot report. This exercise checks both record identities and quantities, because a correct-looking grand total can hide a misclassified record.

Scope and starting data

Use an editable native Google Sheets spreadsheet in a desktop browser, with a disposable practice tab. The exercise uses ordinary table controls, not Gemini, Connected Sheets or conditional email notifications. It is intended for a free personal account; no signed-in application session was used to establish availability. If the table/grouping controls are absent, stop this application exercise rather than upgrading or assuming another edition behaves identically.

Enter this original fixture in A1:D7. Leave no blank row between records. Quantities are numeric whole units, not prices or text labels.

Request ID Category Item Units
R101 Paper Notebook 4
R102 Cables USB cable 3
R103 Paper Envelopes 6
R104 Storage Folder 2
R105 Cables Adapter 5
R106 Paper Labels 1

Before grouping, reconcile the six distinct request IDs and the total of 21 units: 4 + 3 + 6 + 2 + 5 + 1. Preserve this input table or a separate copy as your check against later edits. Do not use the order in which groups appear as evidence of correctness.

Create the grouped view

Select A1:D7 and choose Format > Convert to table. Use Text for the three label columns and Number for Units. In the Category column menu, choose Group by column. Google’s table help also documents Views > Create group by view.

In the category summary rows, use the aggregation controls to select Count for Request ID and Sum for Units. Check the labels instead of trusting automatically assigned aggregations. These commands and available aggregation types are described in Google’s table help.

The expected evidence is:

Category Request IDs belonging to the category Count Sum of Units
Paper R101, R103, R106 3 11
Cables R102, R105 2 8
Storage R104 1 2

Read Count as the check for this deliberately complete ID column, not as a general proof that IDs are unique. Inspect the six IDs separately. The three group counts must add to six, and the three unit sums must add to 21. Those two reconciliations test different things.

Save, refresh and challenge the result

New table views are temporary until saved. With edit permission, choose Save view; reopen the saved view from the table menu after refreshing the spreadsheet. Use Views > View options > Refresh view to refresh its presentation when needed. These lifecycle controls are also documented in Google’s table help.

Now change only R105’s Units from 5 to 7. Keep its Category as Cables. Locate the record by ID rather than assuming a physical row position inside a grouped view. Refresh the view and compare the results:

  • Paper remains three requests and 11 units.
  • Cables remains two requests but becomes 10 units.
  • Storage remains one request and 2 units.
  • All six requests now total 23 units.

Next, change only R106’s Category from Paper to Storage. Paper should contain R101 and R103, with count 2 and units 10. Storage should contain R104 and R106, with count 2 and units 3. Cables stays at count 2 and units 10. The grand total is still 23: reclassification moved one unit between categories but did not create or remove it.

Restore R106 to Paper and R105 to 5 units. Recheck the original 3/2/1 group counts and 11/8/2 sums. This reversal is more useful than merely undoing until the screen looks familiar.

Troubleshooting

Units shows a record count rather than a quantity total: Inspect the selected aggregation. A group containing 3 and 7 has two records but ten units. Both numbers can be legitimate; only one answers the quantity question.

The arithmetic agrees but a request is in the wrong group: Compare IDs with the expected category membership above. The reclassification test deliberately demonstrates why checking only 23 is insufficient.

A record is missing: Check the table’s range and the active view’s filtering settings against all six IDs. Do not delete and recreate production data to repair a view.

The view disappears on reload: Check whether it was saved, not merely created. Saving requires edit access; this exercise does not promise persistent viewer-only views.

You need a separate analysis report: Use pivot tables instead. For table types and identifier preservation, see keep SKU codes as text. For a named filtered working view, see filter without changing coworkers’ views.

Verification limits

The fixture’s memberships, counts, sums and reversals were independently calculated. The table interface, refresh behavior and saved-view reopening remain application checks, not completed native tests. No screenshot or downloadable workbook is presented as execution evidence. Documentation basis: Google Docs Editors Help, reviewed 22 October 2026.