- Getting started with Airtable
- Introduction to Airtable basics
- Contacting Airtable Support Updated
- Airtable home screen
- Glossary of Airtable terminology
- Airtable technical requirements
- Feature differences between Airtable on desktop and mobile
- Airtable keyboard shortcuts
- Using Markdown in Airtable
- Adding descriptions in Airtable
- Finding Airtable IDs
- Airtable Automations
- Automations Overview
- Automation feature walkthroughs
- Integrated automation walkthroughs
- Airtable automation walkthroughs
- Linking existing records using automations
- Conditional groups of automation actions
- Repeating groups of Airtable automation actions
- Creating recurring records using automations
- How to delay Airtable automation runs
- Prevent automations from triggering by mistake
- Use automations to timestamp status updates
- Automation Triggers
- Airtable Triggers
- Airtable automation trigger: When record matches conditions
- Airtable automation trigger: When a form is submitted
- Airtable automation trigger: When record created
- Airtable automation trigger: When record updated
- Airtable automation trigger: When record enters view
- Airtable automation trigger: At scheduled time
- Airtable automation trigger: When webhook received
- Airtable automation trigger: When a button is clicked
- Airtable automation trigger: When email received Updated
- Integrated Triggers
- Airtable Triggers
- Automation Actions
- Airtable Actions
- Airtable automation action: Send email Updated
- Airtable automation action: Create record
- Airtable automation action: Update record
- Airtable automation action: Find records
- Airtable automation action: Sort list
- Airtable automation action: Run a script Updated
- Airtable automation action: Generate with AI
- Integrated Actions
- Airtable automation actions: Slack
- Airtable automation actions: Google Workspace
- Airtable automation action: Send MS Teams message
- Airtable automation actions: Outlook
- Airtable automation actions: Jira Cloud
- Airtable automation actions: Jira Server / Data Center
- Airtable automation actions: Salesforce
- Airtable automation action: Create post in Facebook Pages
- Airtable automation actions: GitHub Issues
- Airtable automation action: Hootsuite post
- Airtable automation action: Send Twilio SMS
- Airtable Actions
- Airtable Bases
- Using Airtable Cobuilder
- Airtable bases overview
- Creating and managing Airtable bases
- Structuring bases in Airtable
- Moving bases between workspaces in Airtable
- Creating and managing tables in Airtable
- Creating Airtable base share links
- Importing third-party data into Airtable
- Using insights in Airtable
- Troubleshooting Airtable base performance
- Airtable Betas
- Collaborating in Airtable
- Airtable Enterprise Support
- General Enterprise information
- External badging in Airtable
- Using app library and components in Airtable Updated
- Ask an Expert beta overview
- European data residency at Airtable
- Airtable user groups overview
- Airtable Enterprise API
- Creating and managing data retention policies in Airtable
- eDiscovery APIs in Airtable
- Airtable and data loss prevention
- Accessing Enterprise audit logs in Airtable
- Set up Jira Server / Data Center to connect with Airtable
- Admin panel pages
- Airtable admin panel overview
- Users - Airtable enterprise admin panel
- Airtable admin panel user details
- Groups - Airtable admin panel
- Workspaces - Airtable Enterprise Admin Panel
- Bases - Airtable admin panel
- Interfaces - Airtable admin panel
- Data sets - Airtable admin panel
- Managed apps - Airtable admin panel
- Components - Airtable admin panel
- Reports - Airtable admin panel
- Settings - Airtable admin panel Updated
- Managing Enterprise organizations
- Managing Enterprise admins in admin panel
- Using Organizations
- Organization branding for apps in Airtable
- Enterprise Hub in Airtable
- Enterprise Hub: Org unit assignment with user groups Updated
- Deactivating, removing access, and reactivating users in the admin panel
- Managing user access to workspaces and bases
- Airtable Enterprise Key Management Updated
- Custom terms of use New
- Enterprise SSO
- General Enterprise information
- Airtable Extensions
- Airtable Fields
- Fields Overview
- Attachment
- Date-based fields
- Formula
- Getting Started with Formulas
- Formula Foundations
- The essentials of Airtable formulas
- Formula writing tips for beginners
- Troubleshooting formulas
- Basic calculations
- Conditional statements
- Logical arguments
- Working with dates
- Displaying DATETIME_FORMAT using the date field in Airtable
- Working with date functions in Airtable
- Calculating the difference between dates in Airtable
- Supported DATETIME_DIFF unit specifiers in Airtable
- Supported DATETIME_FORMAT format specifiers in Airtable
- Using the DATETIME_PARSE() formula in Airtable
- Working with timezones
- Record functions
- Text functions
- Numeric functions
- Common Solutions: Beginner
- Common Solutions: Intermediate
- Common Solutions: Advanced
- Long Text Field
- Linked Record Field
- Linking records in Airtable
- Limiting linked record selection to a view in Airtable
- Dynamic filtering in linked record fields
- Linking to one, many, or a subset of Airtable records
- Converting existing fields to Airtable linked records
- Reordering record links in Airtable
- Understanding linked record relationships in Airtable
- Number-Based Fields
- Other Fields
- Rollup, lookup, and count fields
- Select and user fields
- Integrating with Airtable
- API
- Getting started with Airtable's Web API
- Creating personal access tokens
- Airtable Webhooks API Overview
- Service accounts overview
- Airtable Web API - Using filterByFormula or sort parameters
- Airtable API Deprecation Guidelines
- Airtable API: Common troubleshooting
- Managing API call limits in Airtable
- URL length limitations for web API requests
- Integration services
- Third-party integrations via OAuth overview
- Troubleshooting disconnected OAuth integrations in Airtable
- Options for integrating with Airtable
- Third-party integrations - Common troubleshooting
- Low-code integrations - Common troubleshooting
- Integrating Airtable with external calendar applications
- Visualizing records from Airtable in Tableau
- Visualizing Airtable records in Microsoft Power BI & Power Query
- Integrating HubSpot with Airtable
- Using Zapier to integrate Airtable with other services
- Using Zapier's Multi-Step Zaps to find and update records
- Using IFTTT to integrate Airtable with other services
- Integrating with AWS Lambda & DynamoDB
- Developer tools
- API
- Airtable Interface Designer
- Interface Designer overview articles
- Interface layouts
- Interface elements
- Adding and removing elements in interfaces
- Adding layouts to interfaces
- Formatting elements in interfaces
- Interface element: Button
- Interface element: Calendar
- Interface element: Chart
- Interface element: Filter
- Interface element: Gallery
- Interface element: Grid
- Interface element: Kanban
- Interface element: Number
- Interface element: Record picker
- Interface element: Text
- Interface element: Timeline
- Learning and Resources
- Managing Airtable
- Airtable Policy
- Airtable Records
- Airtable Sync
- Airtable Views
- Airtable Workspaces
- Print
- Share
- DarkLight
- PDF
Dynamic filtering in linked record fields
- Updated on 03 Jan 2025
- 5 Minutes to read
- Print
- Share
- DarkLight
- PDF
Paid plans only | |
| |
Platform(s) | Web/Browser, Mac app, and Windows app, iOS and Android apps*
|
Related reading | |
|
Dynamic filtering in linked record fields overview
Dynamic filtering in linked records supports static filtering on any field type and dynamic filtering on text, number, user, date, select, and linked record field types.
Fig 1.
In this configuration, the filter narrows down employee records—only detailing those individuals with the required skill(s).
Fig 2.
"Design" as the "Skill required " is selected in this configuration.
Using dynamic filtering in linked record fields
NOTE
Dynamic filtering in linked records supports static filtering on any field type and dynamic filtering on text, number, user, date, select, and linked record field types. Supported column types include: text-based columns (single line text, phone, email, long text), number-based columns (number, rating, count, currency, percent, duration), checkbox, users, date, select, multi-select, formula, and rollup fields.
Using static or dynamic conditions in linked records
NOTE
Filters can be stacked on top of each other— allowing you to use both static and dynamic filters simultaneously.
Visit your Airtable homepage.
Open your preferred base.
Locate your linked record field and click the ⌄ icon.
Select Edit field.
Toggle on Filter record selection by a condition.
Click Add condition.
Click the ⚙️ icon and select Static condition or Dynamic condition.
Using dynamic conditioning in text, number, user, and linked records
Dynamic conditioning in text, number, user, and linked records
The left and right operands must be the same field type, as dynamic filters don't support comparing different types. For example, comparing text fields to linked records, number fields to the text fields, etc., isn't supported.
Example: Dynamic conditioning in text, number, user, and linked records
In the example below, the "People" linked record field is filtered by the "Skills" linked record on the "People" table and the "Skills required" linked record on the "Task" table.
Filters can be applied anywhere in bases and interfaces where linked records can be selected.
Dynamic filtering in linked records limitations
The following features are limited when applying dynamic filtering in linked records:
Cross-field type comparison within individual filters
NOTE
Dynamic filtering in linked records doesn't support cross-field type comparison within individual filters.
Example: “Where <User field> has any of <Text field>”
The user field and text field are of different field types, so they cannot be compared using dynamic filtering.
Single select or multi-select fields
NOTE
Dynamic filtering in linked records supports single select or multi-select fields where the filter column must contain all the option names that exist on the dynamic filter column.
Example:Where <Select Field> is <Other Select Field>"
"Select Field" has choices "Todo", "In Progress", "Done", and "Paused" while "Other Select Field" has a subset of these choices, jsut "Todo" and "In Progress". Select and multi-select cell values are compared by exact string matching of option names.
Dynamic filters in forms
NOTE
Dynamic filters on computed fields in forms: Dynamic filters in which the column selected as the right operand is a computed field.
Example: Lookup or count fields are not applied to linked record selections within forms in interfaces and bases.
Date fields
Dynamic filtering in linked records supports date and computed date fields (like Created Time and Last Modified Time), where the two fields are compared using the "exact date" filter mode. The "exact date" filter behaves similarly in dynamic filters as it does in static filters and will compare that the dates or date times are on the same calendar date in the linked record's date field timezone (or on a later date or prior date, etc., as per the filter operator).
Example: "Where <Hire Date> is on or after (exact date) <Task Start Date>"
FAQs
What happens after downgrading a workspace to a Free plan?
After downgrading a workspace to a Free plan, dynamic filtering will continue working, but any applied filters cannot be modified.
Does dynamic filtering in linked records hide records that are already linked?
No, dynamic filtering only affects the selection of new records that can be linked in that specific view. It does not hide or alter the visibility of records that have already been linked or those records that will be linked in other views in the table moving forward. This means that:
Any records linked prior to the application of a dynamic filter will remain visible, regardless of whether they meet the filter criteria.
Any records linked in other views that do not have dynamic filtering will be visible in views that do have dynamic filtering conditions.
Why am I not seeing the field value I need for selection when setting up a dynamic condition?
When seeking to apply dynamic filtering for linked records, it is important to note that if you are using single-select fields or multiple-select fields, you will want to ensure the options match exactly. This includes checking for extra spaces within the available options, making sure there are no extra/missing options between fields, and confirming values have correct upper/lower case characters between the fields.
For example, if a “Status” field in the linked table contains 3 options “Not started”, “In progress”, and “Done” but the “Status” field in the table where you are configuring dynamic conditions contains 4 options “Not Started”, “In progress”, “Blocked”, and “Done ”, then the field will not appear because the “S” in the “Not Started” option is capitalized and there is an extra space in the “Done ” option. You’ll need to correct these options making sure they match the correct capitalization and spacing. Additionally, you’ll need to remove the “Blocked” status option since it doesn’t exist in the other table’s “Status” field or you can add the “Blocked” status option in the other table’s “Status” field so that all the options match.