Airtable linked record pickers: view filters are not validation

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Separate convenience from eligibility

Airtable lets a linked record field restrict the choices shown in its picker to a selected view. Treat that as an aid for manual selection. It does not establish a universal rule that every relationship in your base must satisfy. Write the actual eligibility rule in business language before changing the picker.

Example: active contractors only

Assume an Assignments table should normally link to active contractors. Create an Active contractors view and use it to focus the picker. Now imagine contractor C-14 becomes inactive after an assignment was created. Your operational policy might preserve historical assignments while prohibiting new ones. A picker setting alone cannot express that distinction or explain which historical links should remain.

Configure and inspect

1. Create an eligibility view with an explicit Active condition and verify one included and one excluded fixture.
2. Edit the linked record field and select the view-limited picker option.
3. Open the picker in a new sample assignment and check the visible choices.
4. Review existing assignments separately for links that now fall outside the rule.
5. Review imports and automation mappings independently, rather than inferring their behavior from a manual picker test.

Decide what a violation means

Keep an exception report with assignment ID, contractor ID, assignment date, current eligibility and the reason the link exists. For future bookings, route invalid links to review; for completed bookings, preserve the relationship and explain the historical state. This is an editorial workflow recommendation, not a claim that Airtable automatically enforces those policies.

Acceptance criteria

Approve the change when the intended manual choices are easier to find and the team has a separate method to detect disallowed new assignments. If you require access restrictions, evaluate the actual sharing and permission configuration as a separate task. Hiding an option is not evidence that a person cannot see its record through another permitted surface.

Continue with Airtable junction tables: store facts about a relationship when that next step matches your workflow.