Row Actions

Easy 2 min setup No componentsscrTableRowActions
Download .msapp

The read only table with a more button per row. On desktop the actions open inside the row; on a phone they open as a bottom sheet. Quick look shows the row's fields in a side panel without a query.

Best for: Lists where people do more than open an item.

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

In-row actions

Slide over the row's right-hand columns

Phone sheet

Actions as a bottom sheet

Quick look

A side panel, or a sheet on a phone

Copy number

Copy() plus a notice

How it works

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

1

Why the actions open inside the row

A gallery cannot report where a row sits once scrolled, so a floating menu cannot be anchored to it. The actions take the row's own space instead.

2

Real buttons, not a tab list

A tab list keeps a selection, so a second click on the same action never fires, and screen readers announce it as tabs. Each action is a button.

3

Quick look from the row's own record

Opening the menu stores ThisItem in a variable, so Quick look shows every field without fetching anything.

UpdateContext({ locTraMenuKey: ThisItem.ItemKey, locTraMenuRec: ThisItem })

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.

  1. Add your list as a data source.
  2. In galTraRows.Items, replace colTblItems with your list (the src: Filter(colTblItems, ...) inside the With).
  3. Delete nfSeedTblItems(); from the screen’s OnVisible.
  4. If your columns are named differently, rename them in the screen, or add matching columns to the list.
  5. Index these columns: Title, ItemKey, StatusKey, CategoryKey, Owner, Amount, DueDate.

Specific to this pattern

Edit and Delete show a notice: point them at your edit form and your delete (or soft delete) action.

The columns the patterns read

ColumnTypeUsed for
TitleTextThe item's name; searched and sorted
ItemKeyTextA unique reference, e.g. ITM-0042; searched, and the selection key
OwnerTextWho the item belongs to
OwnerEmailTextThe owner's email
StatusKeyTextNotStarted, InProgress, OnHold or Completed
CategoryKeyTextA key from nfTblCategories
PriorityKeyTextHigh, Medium or Low
AmountNumberA money value
DueDateDateWhen it is due; overdue rows turn red
CreatedDate and timeBuilt 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