Querying and filtering data
Name the table and describe the records you want in chat. Include the conditions and time period that matter.
Ask in chat
Show me all deals over $50,000.
How many open support tickets do we have?
How many records are in my Contacts table?
Use conditions like these to make a request specific. These are ways to describe the result, not a fixed set of controls in every app.
| Condition | Example request |
|---|---|
| Equals | Show records whose status is Active. |
| Contains | Find companies whose name contains Acme. |
| Greater or less than | Show deals with a value greater than 50000. |
| Date range | Show records created between January 1 and March 31, 2026. |
| Empty or not empty | Find contacts without an email address. |
| In or not in a set | Show tickets whose status is Open or In Progress. |
Review the result against the source data, particularly when a condition could mean more than one thing.
Use an app
Ask for the filters, sort order, and page size you need when building an app. For example:
Show open deals sorted by value, highest first, with 25 deals per page.
The controls you see depend on how the app was built and what data you can access. Do not assume every app has the same filters or automatically paginates results.
Reference columns link to records in another table. Access to the source does not automatically give you access to the referenced table. See Creating collections and tables.
Still stuck? Email support@play.fast