Paginated Table
Keyset paging: each page is its own delegable query for the next ten rows after the last one shown, so paging never stops at the data row limit. Previous pages are a stack of cursors.
Best for: Very long lists where people step through pages rather than scroll.
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
Previous and Next
With the page number
Keyset paging
Each page is the next PageSize after a cursor
Knows the end
Fetches one extra row to decide whether Next shows
Filters
Search, status and category restart at page one
How it works
The 2 techniques that make this pattern work on a list big enough to matter.
The cursor is Created, not ID
ID > n does not delegate on SharePoint; Created > date does. Rows are ordered by Created and the page starts after the last row of the previous one.
FirstN(SortByColumns(Filter(src, Created > locTpgCursor),
"Created", SortOrder.Ascending), nfTbl.PageSize + 1)Previous is a stack
Each Next pushes the current cursor onto colTpgCursors; Previous pops it. There is no skip on SharePoint, so a page number cannot be jumped to directly.
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
btnTpgLoad.OnSelect, replacecolTblItemswith your list (the Filter(colTblItems, ...) inside the ClearCollect). - 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:
Created,Title,ItemKey,StatusKey,CategoryKey.
Specific to this pattern
Index Created; it is the paging key.
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