Filters in views help you organize and focus on specific records in your table by applying custom criteria. When a record is excluded due to a filter, it isn’t deleted; it’s simply hidden from the current view. This guide provides an overview of how to create and manage filtering conditions to optimize your workflow.
Plan Availability | All plan types |
Permissions | Solution Creators: Can create, modify, delete, and manage filters in the Solutions they have access to. |
Platform | Web, Mobile iOS, Mobile Android. |
Related Reading |
What changed
26 Oct 2026. The AND and OR comparison sentence was rewritten as the present fact and the release is listed below. No product behavior, limit or price changed; the Last verified date at the end is the date of this edit.
Product changes to filters, newest first, each with its What's New post.
14 Sep 2026: Calendar periods and rolling ranges with custom units in date filters; see the release post.
A condition is a rule you establish, dictating which records are displayed within a given view. Consider adding conditions when:
You need to swiftly locate records that meet specific criteria (e.g., records with a due date after X date and before Y date).
You want to focus solely on records that satisfy certain conditions (e.g., records assigned to me AND not marked as completed).
Certain records in a shared view link need to be hidden from certain individuals. A compelling example of condition usage is archiving the accounts that are no longer active.
Conditions
Conditions allow you to filter out records within the view are you working in.
Think of a condition as a sentence that describes the data you are looking at. For example, show me the records where the Project Owner is Emma.
Conditions are made up of three parts:
Field- The field in your Table that you want to use for filtering.
Operator - Once the field is selected, you can choose the operator from the dropdown.
The filter operators available depend on the field type. For example, a Date field has filter operators such as "is on", "is before," and "is after". Whereas, Text fields have operators such as "contains," "does not contain," "is empty/not empty."
Value: This represents the value you will compare your records against.
Creating a condition
For example, we have a Table with several different types of properties with a single select field called Type that labels each property.
We would like to display only the records that are Residential properties. To add a new filter condition to the view, click on "Filter" in the reporting toolbar.
When creating the condition, think about the overall statement as a sentence. In this case, we need a view that shows only the properties that are residential.
The condition breakdown:
Field to be assessed - the "Property Type" field.
Operator - We want to make sure the Property Type is "Residential".
Value - Lastly, we enter the specific value we need to meet the condition. "Residential" is the value we need to achieve this view.
The final condition: Where [Property Type] is [Residential].
Removing a condition
To remove a condition, click the X next to the condition.
Conditions & Conjunctions
In real-world workflows, requests are more complex than "Show me all residential properties". They combine conditions, such as "show me the residential properties AND confirm they have available units", or weigh priorities, such as "show me residential OR commercial properties".
To effectively sift through records and create meaningful views, it's essential to use a combination of conditions that can accommodate these complexities.
Using Conjunctions
You have the option to logically link conditions into a condition group using conjunctions. The two available conjunctions are "AND" and "OR":
Use "AND" when you require all conditions in a group to be satisfied.
On the other hand, use "OR" when you want any condition within a group to be met.
For example, above, two conditions are linked within the conjunction group using "OR."
This can be interpreted as "Display records where Emma is the Project Manager or where Emma is on the Project Team".
Using the "AND" Conjunction
We can use conjunctions to link multiple conditions and construct more detailed filters. The AND conjunction creates a condition group that requires the records to meet all the conditions specified. For example, show me all the residential properties that have available units.
Two conditions are involved:
Where [Property Type] is [Residential] AND
[Available Units] (a Count field) greater than 1.
Using the "OR" Conjunction
Use the OR conjunction when you want any of the conditions in the group to be met.
For example:
Where [Property Type] is [Residential] or
Available Units is greater than 1.
Toggling between AND & OR
NOTE: When using the "And" conjunction: every condition within a group must align for a record to meet the criteria of that filter. Conversely, with the "Or" conjunction: any of the conditions within a group can be satisfied for a record to meet the filter's requirements.
To emphasize the distinction between using the "And" conjunction and the "Or" conjunction, let's observe the outcome when we switch from one to the other. In the GIF below, we start with a condition group that states: "[Property Type] [is] [Residential] AND [Available Units] is [greater than] [1].
Utilizing the "Or" conjunction implies that any condition within the group can be met. Consequently, instead of displaying records that meet both "Residential AND the Available Units is greater than 1," we present records that satisfy either "Residential OR the available units is greater than 1". Selecting the appropriate conjunction can have a significant impact on the outcome.
Filter Groups
Filter groups allow you to construct views that display just the right set of data for a particular workflow, narrowing down the data that is presented to match complex criteria that you specify.
Use filter groups to specify a set of conditions that contain AND or OR conditions that should be matched. Filter groups allow you to combine AND and OR operators within the same filter.
For more information on how to use filter groups, read this article.
Operator Options Based on Field Type
Numeric, Date, Values List and Text field types have distinct filter operators to use in combination with the filter criteria.
Filtering with Numeric Fields
Numeric field operators include: equal to, not equal to, greater than, less than, equal to or greater than, equal to or less than, is empty, is not empty.
Entering a value in the criteria field automatically applies the filter to the current view or saved view.
Filtering with Date Fields
Date field operators include: is, is not, is before, is after, is on or before, is on or after, is empty, is not empty.
Select an operator in combination with a filter criteria:
- Today, Tomorrow, Yesterday.
- Calendar periods: Previous, Current, or Next week, month, quarter, or year.
- Rolling ranges: The next number of … or The past number of …, with a unit selector for days, weeks, months, quarters, or years.
- Exact Date / Range.
Calendar periods match real calendar boundaries. For example, Next month always covers the entire upcoming calendar month, and Current quarter covers the calendar quarter that includes today.
Rolling ranges count forward or backward from today by the number and unit you choose, for example, "the next 2 weeks" or "the past 3 months".
On mobile, the filter also shows a summary line under the value control confirming the exact date range it matches, so you can check it before saving.
Additional filter criteria is required when a Rolling range (The next number of … or The past number of …) or Exact Date / Range is selected. For Rolling ranges, this includes both a number and a unit (days, weeks, months, quarters, or years).
The count for a rolling range accepts whole numbers up to 999.
Week boundaries follow the locale set in your profile, so teams whose weeks start on different days each see their own week.
The comparison operators (is before, is after, is on or before, is on or after) accept calendar periods: before a period means before its first day, after a period means after its last day.
First Created and Last Updated offer Previous and Current periods and "The past number of" only; they never offer future options.
Each date condition shows the exact date range it resolves to beneath the row.
Filtering with Values List Fields
Values List field operators include: is, is not, is any of, is none of, is empty, is not empty.
The field criteria field automatically loads the values list. When the " is any of " or " is none of " operators are selected, multiple values can be selected in the same filter.
Filtering with Text-based Fields
Text-based field operators are: is, is not, is empty, is not empty, contains, does not contain.
Text-based fields for the purpose of filtering include Text, Text Area, SmartDoc and Linked Record fields.
Text filters can be applied to Files & Image fields.
Using Multiple Filters
Pare down your data to the perfect saved view using multiple filters at once. Select between AND/OR for each filter level.
Filters are applied instantly and saved automatically. Click CLEAR ALL to remove all filter criteria, or click the trash icon to remove filters one at a time.
Filtering with Checklist Field
Checklist fields have their own operators: all items resolved, not all items resolved, percent complete is greater than, and percent complete is less than.
Filtering with View Types
Filtering in Grid View
Grid view supports quick filtering with the Column Controls.
Filtering in Card & Kanban View
Filters instantly remove cards from view.
Filtering in Calendar, Timeline & Map Views
Filtering in Calendar, Timeline and Map views reorders cards in the Record Listing panel and removes records from view.
Pro tip: Filter by Current User
Create one report that will allow everyone on your team to see the work assigned to only them (the Current User).
Follow these steps:
Go to the desired Saved View.
Click on Filter in the Toolbar.
Select the Assign To Field you want to filter by... 'is exactly' ... Current User
Now, any time a user access this saved view, they will only see fields assigned to them; no need for a separate saved view for everyone.
Practical Scenarios and Use Cases
Departmental Collaboration
Scenario: The marketing team needs focused data for campaigns.
Solution: Use filters to show campaign-related records only.
Project-Specific Access
Scenario: Sensitive project data should be accessible to key members only.
Solution: Create a filter to show relevant records while hiding sensitive data.
Dynamic User Views
Scenario: Each user needs to see their tasks without creating separate views.
Solution: Apply a "Current User" filter to a shared view.
Frequently asked questions
Does a filter delete the records it hides?
Does a filter delete the records it hides?
No. A record excluded by a filter is hidden from that view only; it stays in the table and in every other view.
Can I combine AND and OR in one filter?
Can I combine AND and OR in one filter?
Yes. Filter groups let a group of OR conditions sit inside an AND filter, or the reverse; see Advanced Filtering Using Filter Groups.
How do I show each member only their own records?
How do I show each member only their own records?
Add a condition on the assignee field with the operator is exactly and the value Current User. One saved view then shows each member their own records; see Filter by Current User.
Do I have to save a filter?
Do I have to save a filter?
No. Filters apply instantly and are saved automatically with the view. CLEAR ALL removes every condition; the trash icon removes one.
How far can a rolling date range reach?
How far can a rolling date range reach?
The count for The next number of or The past number of accepts whole numbers up to 999, with days, weeks, months, quarters or years as the unit.
Last verified 26 Oct 2026.