From d6a2220ce60b5d4bafeda6543de7fb5511e9da5f Mon Sep 17 00:00:00 2001 From: Hugh Messenger Date: Sat, 28 Feb 2026 05:38:02 -0600 Subject: [PATCH] [4.x] docs: Add note about refreshing table from actions when using custom data (#19374) * Add note about refreshing table from actions when using custom data * Update 09-custom-data.md --------- Co-authored-by: Dan Harrin --- packages/tables/docs/09-custom-data.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/packages/tables/docs/09-custom-data.md b/packages/tables/docs/09-custom-data.md index baa2d14322..c5636f4d56 100644 --- a/packages/tables/docs/09-custom-data.md +++ b/packages/tables/docs/09-custom-data.md @@ -374,6 +374,10 @@ public function table(Table $table): Table } ``` + + ### Bulk actions For actions that interact with a single record, the record is always present on the current table page, so the `records()` method can be used to fetch the data. However for bulk actions, records can be selected across pagination pages. If you would like to use a bulk action that selects records across pages, you need to give Filament a way to fetch records across pages, otherwise it will only return the records from the current page. The `resolveSelectedRecordsUsing()` method should accept a function which has a `$keys` parameter, and returns an array of record data: @@ -412,7 +416,7 @@ public function table(Table $table): Table ->columns([ // ... ]) - ->recordActions([ + ->toolbarActions([ BulkAction::make('feature') ->requiresConfirmation() ->action(function (Collection $records): void { @@ -476,7 +480,7 @@ public function table(Table $table): Table ->columns([ // ... ]) - ->recordActions([ + ->toolbarActions([ BulkAction::make('feature') ->requiresConfirmation() ->action(function (Collection $records): void {