How do you limit and sort a Xano-backed list in Adalo?
Move list limits, pagination, and sorting into the Xano endpoint when Adalo does not show its standard Max Items or Sort controls.
Short answer
Set limiting and sorting on the Xano GET All endpoint instead of looking for Adalo’s standard Max Items and Sort controls. Add lowercase limit and offset inputs for pagination, apply an explicit sort in Xano, publish the endpoint, and confirm the returned count and order in Adalo.
The intended outcome
A Xano-backed list returns a deliberate number of records in a stable order without relying on controls that are unavailable for that external collection.
Treat the external endpoint as the source of truth for result size and order. Configure Xano’s GET All endpoint to return a bounded, deterministically sorted array, publish the endpoint, and verify its response against the Adalo list rather than assuming native-collection controls are available.
Requirements
- A Xano-backed External Collection connected to the list
- Access to the collection’s GET All endpoint in Xano
- Representative records with a field that can be sorted deterministically
Step by step
Step 1: Confirm the external data source
Verify that the list uses a Xano or other External Collection; native Adalo collections expose a different set of list controls.
Step 2: Add pagination inputs in Xano
Open the table’s GET All endpoint and add lowercase integer inputs named limit and offset. These names are case-sensitive in the documented Adalo integration.
Step 3: Configure the endpoint response
Enable paging on the Xano query, map Per Page to limit and Offset to offset, and leave paging metadata off so Adalo can load the returned array correctly.
Step 4: Apply a deterministic sort
Set the desired sort inside the Xano query or expose the exact query parameter your endpoint expects. Include a tie-breaker such as record ID when the primary sort field can repeat.
Step 5: Publish and retest
Publish the Xano endpoint, retest or reconnect the External Collection in Adalo if its inputs changed, then preview the list and compare its count and order with the endpoint response.
The underlying logic
Adalo renders the records returned by an External Collection endpoint, so the provider’s GET All behavior is the reliable place to bound and order the result when native list controls are absent.
Explicit limit, offset, and sort behavior makes pagination repeatable; an unspecified order can move records between pages or change which item appears first.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| External Xano records | A stable ID plus the field or fields used for sorting | Defined by the Xano schema and exposed through the External Collection response |
What still needs checking?
- This is a forum-native answer with no original Adalocado video; current Adalo documentation now gives an explicit limit/offset pagination workflow for Xano lists.
Common failure modes
Confirm the Xano inputs are exactly lowercase limit and offset, paging metadata is off, the response remains an array, and the endpoint changes were published.
Add a deterministic secondary sort, such as record ID, and verify the endpoint applies the same order before limit and offset are calculated.
Testing checklist
0 of 7 checked on this device
Current limitations
- Current Adalo documentation defines Xano’s limit and offset pagination setup, but the exact sort field or query-parameter names depend on the Xano endpoint you build.
- Adalocado has not reproduced this workflow in a current project, so test the published endpoint and Adalo list together before relying on it in production.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Don’t see Max Items in Simple List
The accepted reply identifies the list as an external Xano collection and directs limiting and sorting to provider-specific query parameters rather than missing native list controls.
Boundary: The reply does not name a universal Xano sorting parameter, because that contract depends on the endpoint.
SynopsisLabs (question) and Dilon (accepted answer) · April 2026
Sources and status
This page was last reviewed on Aug 14, 2026. Its current status is Documented from current sources.
Verification owner: Adalocado editorial. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
