Explain the absence
Users need to know whether there truly is no data or whether their current filter removed it.
Show a Message when Query Returns No Results
In some cases your query may return no results so it is useful to be able to show a message, telling the users no results are returned. In Wappler this can be d
No Results State
Section titled “No Results State”Show an honest no-results state so filtered or empty datasets explain themselves instead of making the page feel broken.
Introduction
Section titled “Introduction”A no-results state is not filler. It is part of the data-display contract. When a filter, search, or empty dataset removes visible rows, the page should explain what happened so users can recover confidently instead of assuming the app failed. In Wappler, that usually means conditional display driven by the current result size, not a hard-coded empty paragraph disconnected from the actual state.
Offer a path forward
A good empty state helps users reset, broaden, or understand the current view.
Tie the no-results state to real list state.
Explain whether the dataset is empty or only filtered away.
Suggest the next action when recovery is possible.
Keep the empty state as intentional as the filled state.
Make empty states informative
Section titled “Make empty states informative”Blank space is not an explanation.
Distinguish empty data from filtered-out data
Section titled “Distinguish empty data from filtered-out data”A brand-new dataset with no records is different from a populated dataset that currently has no matches. The message should reflect that difference whenever possible.
Better guidance
Users recover faster when the page explains which kind of empty state they are seeing.
Connect the message to the current controls
Section titled “Connect the message to the current controls”If a search term or filter caused the empty state, the page should make that relationship obvious. Otherwise users may not connect the blank result to their own current inputs.
Context matters
The empty state should reference the active narrowing conditions when that helps.
Leave users a way out
Section titled “Leave users a way out”Resetting filters, clearing search, or navigating to create a first record are common next steps. An empty state is stronger when it points to a useful recovery path.
Actionable UI
A helpful empty state guides the next click instead of only describing the problem.
Next steps
Section titled “Next steps”No-results states pair naturally with text filters, checkbox filters, and total counts that explain the current view.
Interaction
Section titled “Interaction”Wire events to actions, and work with Dynamic Events/Attributes.
Interaction
Section titled “Interaction”Choose an Interaction tour to start. These tours focus on wiring events to actions and using Dynamic Events/Attributes to keep behavior declarative.