- 05 Dec 2024
- 5 Minuten zu lesen
- Drucken
- DunkelHell
- pdf
Dynamic filtering in linked record fields
- Aktualisiert am 05 Dec 2024
- 5 Minuten zu lesen
- Drucken
- DunkelHell
- pdf
Team, Business, and Enterprise Scale plans | |
| |
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.