From a32dd9efeedf0ffdca35ecdeba04363437cebbd9 Mon Sep 17 00:00:00 2001
From: Hugh Messenger <hugh.messenger@gmail.com>
Date: Thu, 19 Feb 2026 04:06:07 -0600
Subject: [PATCH] Add note about multiple paginators with custom tables
 (#19279)

* Add note about multiple paginators with custom tables

* chore: fix code style

* Update 09-custom-data.md

---------

Co-authored-by: cheesegrits <cheesegrits@users.noreply.github.com>
Co-authored-by: Dan Harrin <git@danharrin.com>
---
 packages/tables/docs/09-custom-data.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/packages/tables/docs/09-custom-data.md b/packages/tables/docs/09-custom-data.md
index 347db7480c..baa2d14322 100644
--- a/packages/tables/docs/09-custom-data.md
+++ b/packages/tables/docs/09-custom-data.md
@@ -329,6 +329,10 @@ In this example, the `forPage()` method is used to paginate the data. This proba
     It might seem like Filament should paginate the data for you, but in many cases, it's better to let your data source—like a custom query or API call—handle the pagination instead.
 </Aside>
 
+<Aside variant="warning">
+    If you have multiple custom tables on a page and are using the `queryStringIdentifier('customIdentifier')` method to distinguish them, you will need to add an `options` argument to the `LengthAwarePaginator` with the `pageName`, like `options: ['pageName' => 'customIdentifierPage']`. Note that adding the `Page` suffix to your custom identifier is required here.
+</Aside>
+
 ## Actions
 
 [Actions](actions) in the table work similarly to how they do when using [Eloquent models](https://laravel.com/docs/eloquent). The only difference is that the `$record` parameter in the action's callback function will be an `array` instead of a `Model`.