Glide provides two different ways to filter data: Screen Filtering and Collection Filtering. While they sound similar, they work in distinct ways. Understanding the difference is key to building apps that display data the way you intend.
Screen Filtering
A screen filter applies to the screen’s data source.
How it works:
When you create a screen, it automatically points to a table.
When there are no collections on the screen, you can add a screen filter. This is meant to narrow that data down to one row.
If no filter is set, the screen defaults to showing the first row in the table.
Use case: Commonly used for things like showing the signed-in user’s profile row.
Limitation: The filter only applies to the screen’s own data. If you add a new collection (like a list) to the screen later, that collection won’t inherit the screen filter.
Collection Filtering
A collection filter applies only to the data inside a specific collection component (e.g. list, table, grid).
How it works:
Each collection points at its own data source.
You can add filters to narrow the rows displayed in that collection, regardless of the screen’s filter.
Use case: Displaying only rows that meet certain conditions, such as “Orders where UserID = Signed-In User.”
Independence: Collection filters do not depend on screen filters. They are applied directly to the collection’s dataset.
Key Difference
Screen filter: Restricts the screen’s data source to one row.
Collection filter: Restricts what rows show inside a single collection.
If you filter a screen, that does not automatically limit any collections you add later. Collections need their own filters.
Best Practices
Use Screen Filtering to give a screen its context about a single row (e.g. “this screen shows just one person’s data”).
Use Collection Filtering to control what appears in lists, tables, or other collection components on that screen.
Don’t assume screen filters cascade into collections — always set collection filters explicitly when you need them.