Grouped Table

Easy 2 min setup No componentsscrTableGrouped

Groups with headers, counts and an expand control, plus Expand all. Each open group is its own delegable query, so a large closed group costs nothing.

Best for: Lists people scan by state: what is open, waiting, done.

Two parts to paste. The Screen YAML and the App.Formulas. The formulas are the same for all ten patterns, so an app with several of them needs that block once. Without it the screen has no colours, sizes or sample rows — or download the .msapp to skip the paste.

Preview and code

Wireframe — screenshots coming soon

Group headers

Chevron, name, count, Expand or Collapse

Expand all

One toggle for every group

Per-group query

Only open groups load rows

Filters

Search, status and category apply inside groups

How it works

The 2 techniques that make this pattern work on a list big enough to matter.

Groups are the status table, not a GroupBy

GroupBy over a list does not delegate. The groups are the four statuses, and each open one runs its own Filter on StatusKey, which is indexed.

Flattened into one gallery

btnTgrLoad writes group headers and their rows into colTgrRows with a sort key, and the gallery shows that in order, so headers and rows share one scroll.

Connect to SharePoint

It ships on sample rows. The queries are already written the way SharePoint needs, so switching is a rename rather than a rewrite.

Add your list as a data source.
In btnTgrLoad.OnSelect, replace colTblItems with your list (the Filter(colTblItems, ...) per open group).
Delete nfSeedTblItems(); from the screen’s OnVisible.
If your columns are named differently, rename them in the screen, or add matching columns to the list.
Index these columns: StatusKey, Title, ItemKey, CategoryKey.

Specific to this pattern

A count shows for open groups only: a count of a closed group would be an aggregate over the list, which does not delegate.

Each open group loads into a collection, so a single group is capped at the data row limit (up to 2,000). Use it where every group stays well under that; for one huge group, use the Paginated pattern instead.

The columns the patterns read

Column	Type	Used for
Title	Text	The item's name; searched and sorted
ItemKey	Text	A unique reference, e.g. ITM-0042; searched, and the selection key
Owner	Text	Who the item belongs to
OwnerEmail	Text	The owner's email
StatusKey	Text	NotStarted, InProgress, OnHold or Completed
CategoryKey	Text	A key from nfTblCategories
PriorityKey	Text	High, Medium or Low
Amount	Number	A money value
DueDate	Date	When it is due; overdue rows turn red
Created	Date and time	Built in on a SharePoint list

Rules that keep it working past 5,000 rows

Every filter on a growing list must delegate: equality on an indexed column, StartsWith on text, and And or Or of those. in, Search() and <> do not delegate on SharePoint.
An "All" choice must send no condition. Put the If outside the Filter and test the key with IsBlank, never with = "": a blank key compared with a column filters on blank and returns nothing.
Sort with one literal SortByColumns per column. A column name held in a variable does not delegate.
Index every column you filter or sort on before the list passes 5,000 items. Past that, SharePoint refuses an unindexed filter or sort outright.
CountRows, Sum and Average do not delegate. Show rows loaded rather than a total, or keep totals in a list a scheduled flow maintains.

Get new components and templates when they drop

One email when something new ships. Unsubscribe anytime.

Community

Use the toolbar to format · or type markdown directly