Lists in Adalo, from data to layout
Connect a list to a collection, bind fields with Magic Text, filter the records, and understand when a custom list is worth the complexity.
We checked current official documentation, captured the relevant screens, and compared the workflow with dated Adalo forum reports. Source links and limitations are below so you can judge the evidence directly.
Choose the collection under “What is this a list of?”, bind each visible field to the current record with Magic Text, then add filters and sorting only after the base list returns the correct records.
Treat a list as a query before treating it as a design element. Connect it to the correct collection, prove the expected records appear, bind repeated fields to the current record, and only then add sorting and filters. This sequence isolates data errors from layout errors and makes the empty state a deliberate product decision.
The intended outcome
A list that shows the intended collection, presents useful fields, opens the right detail record, and handles an empty result.
Requirements
- A collection with sample records
- A screen that can access the data
- Understanding of Magic Text
Step by step
- 01
Add a list
Place a standard or custom list on the screen. Start with the simplest list that can express the layout.
- 02
Choose its collection
Set “What is this a list of?” to the collection whose records should repeat.
- 03
Bind the visible fields
Select each text or image inside the list and use Current [record] Magic Text to display the correct property.
- 04
Add filters deliberately
Add a custom filter for each rule. Current documentation supports multiple list filters with AND/OR logic.
- 05
Sort and link
Choose a stable sort, then link the repeated item or button to a detail screen while passing Current [record].
- 06
Design the empty state
Explain why no records are visible and provide the most useful next action.
The underlying logic
A list repeats one design for every record returned by its query.
Filters decide which records enter the list; visibility decides whether one component appears.
Custom lists increase layout freedom but can also increase component count and maintenance.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| Items | Name, Description, Status, Created Date | Belongs to one owner and optionally one category |
| Categories | Name, Sort Order | Has many items |
What changed?
- Current documentation supports multiple list filters with explicit AND or OR behavior.
Start with the query
Treat the list as a query before treating it as a visual component. Prove the right records are returned, then style the repeated row.
Filters versus conditions
Filters refine groups of records. Conditions control whether an action runs or a component appears. Mixing those responsibilities makes debugging unnecessarily hard.
Performance discipline
Each extra filter, nested relationship, and repeated component adds work. Keep list rows lean and prefer a detail screen for secondary information.
Common failure modes
The list is empty
Temporarily remove custom filters. If records appear, restore filters one at a time and verify their data types and values.
Every item shows the same content
Use Current [record] inside the list rather than screen-level or logged-in user data.
Search misses obvious results
Text equality is case-sensitive; the Contains operator is less strict and better suited to ordinary text search.
Testing checklist
The unfiltered list returns every expected sample record before filters are added.
A selected row opens the matching detail record and preserves its identity.
An empty result displays an explanation and a useful recovery action.
Unfiltered records appear first
Every repeated field uses the current record
The item passes the correct record to details
Empty and loading states are understandable
Filters remain performant
Current limitations
- Deep relationship filters and heavy custom rows can create performance costs.
Screenshot evidence
These captures document what Adalo currently publishes and what builders are reporting. They support the written guidance, but they are not a substitute for an end-to-end test in your own app.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts—not endorsements or independently reproduced results.
Improved Filtering Logic
The changelog says list, count, and dropdown filters were made more consistent and added checks for empty relationships, files, images, and locations.
Boundary: The post says affected apps require a rebuild; existing published builds may not inherit the behavior automatically.
Adalo system · March 2024Sources and status
This page was last reviewed on Aug 12, 2026. Its current status is Verified from current public evidence.
Verification owner: Adalocado editorial. Next review: Nov 12, 2026.
Changelog
Added current official screenshots and Adalo’s filtering changelog as public evidence.
Did this solve your problem?
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
Ask Adalocado
