Creating Airtable forms with linked record dropdowns
Linked records are the best thing about Airtable. They're what separates it from a spreadsheet. You build a Clients table, link it to Projects, link Projects to Tasks, and suddenly you have a real relational database.
Then you try to put a linked record field in a form.
It breaks. Not subtly. The field turns into a raw text input. Users have to type an exact record name to link anything. Typos create duplicates. Nobody knows what to type. The whole point of having linked records is gone.
This is a known problem. It's been a known problem for years. And the fix isn't complicated, but it does require a different tool.
Already frustrated by this? Filla gives you searchable linked record dropdowns in forms, filtered by any view, with the option to create new records inline. Native Airtable integration, no field mapping. Start free →
What actually happens with linked records in native Airtable forms
Here's the exact behavior, so we're on the same page.
You have a Projects table. Each project links to a Client record in your Clients table. You build a form so your team can submit new projects.
When you add the "Client" linked record field to the form, Airtable renders it as a plain text input with a small search icon. If the user knows the exact name of the client record, they can type it and Airtable will find a match. If the name doesn't match exactly, nothing links. If they leave it blank, the project gets created with no client attached.
There's no dropdown. No list of available options. No way for the form user to browse what exists.
For internal teams who know your data, this is annoying. For external users or anyone unfamiliar with your records, it's unusable.
The workaround most people use is to replace the linked record field with a single select field. You manually add all the options, maintain them as clients are added or removed, and then run an automation to convert the text value back into an actual linked record after submission.
It works. It's also a maintenance nightmare. Your single select and your Clients table drift apart. Someone adds a new client, forgets to update the form, and submissions come in with an option that doesn't match anything.
What you actually need from linked record fields in forms
The behavior that makes sense is straightforward.
A searchable dropdown. The form field should show a list of linked record options. Users type to filter. They click to select. The record gets linked. This is how every other relational tool works.
Filtered options. Not every record in the linked table is always a valid selection. You might have active and archived clients. You want the form to only show active ones. You should be able to filter options using an existing Airtable view.
Meaningful display fields. Your client records might have names, account numbers, and regions. The dropdown should show enough information to help users pick the right one, not just a name that might be ambiguous.
Multi-select. Some linked record fields allow multiple links. The form should support that too.
Create new inline (optional). For cases where a user needs to link to a record that doesn't exist yet, being able to create it directly from the form without navigating away is worth having.
None of this is exotic. This is just how linked record selection should work.
How Filla handles linked records in forms
Filla is built specifically for Airtable. Linked records in forms are one of the core things it gets right.
When you add a linked record field to a Filla form, it renders as a searchable dropdown. Users see a list of records from the linked table. They type to filter. They select one (or multiple, if the field allows it). The submission creates a properly linked record in your base.
Three things make this particularly useful.
Filter by view. You control which records appear in the dropdown by pointing the field at a specific Airtable view. If you have an "Active Clients" view that filters out archived records, you use that view and only active clients appear as options. When you add a new client in Airtable and it meets the view criteria, it shows up in the form automatically. No manual updates.
Display fields. You can configure which fields appear in the dropdown to help users identify records. If client names aren't unique, you can show the client name plus their region plus their account ID. Users get the context they need to pick correctly.
Create new records inline. When enabled, users who can't find what they need in the dropdown can create a new linked record without leaving the form. The new record gets created in Airtable and linked in the same submission.
Step-by-step: Setting up linked record dropdowns in Filla
Step 1: Connect your Airtable base
Go to app.filla.io/signup and connect your Airtable account via OAuth. Filla reads your base structure, including all tables, fields, and views. No manual configuration.
Step 2: Create a new form
Select the table where submissions should land. If you're building a project intake form, select your Projects table. Filla pulls in all the fields from that table automatically.
Step 3: Add the linked record field
In the form editor, find your linked record field in the field list (it'll show the linked table name next to it). Drag it into the form or click to add it.
The field renders as a linked record dropdown by default. No extra setup needed for basic functionality.
Step 4: Configure the filter view
Click the linked record field in the form editor to open its settings. You'll see an option to filter by view.
Open the dropdown and select a view from your linked table. Only records visible in that view will appear as options in the form.
If you don't have a filtered view yet, create one in Airtable first. For example, create an "Active Clients" view with a filter for Status = Active. Then come back and select it here.
Step 5: Configure display fields
In the same field settings panel, look for display fields. By default, Filla shows the primary field of each linked record. You can add additional fields to display alongside it.
Click "Add display field" and select any field from the linked table. This is helpful when primary fields alone are ambiguous. For example, if two clients have similar names, adding "Company" or "Account ID" as a display field helps users pick the right one.
Step 6: Set single or multi-select behavior
If your linked record field in Airtable is set to allow multiple linked records, Filla will support multi-select in the dropdown automatically. Users can select more than one option. The selections appear as tags.
If you want to restrict to single selection (even if the field technically allows multiples), you can configure that in field settings.
Step 7: Enable or disable inline record creation
In field settings, there's a toggle for allowing users to create new records inline. This is off by default.
Turn it on if your use case requires it. For example, a volunteer registration form where new organizations might be entering their details for the first time. Leave it off for tightly controlled datasets where you don't want form users adding records.
Step 8: Test the form
Open the form preview and interact with the linked record field. Type a few characters and watch the dropdown filter in real time. Select a record and confirm the selection displays correctly. Submit a test entry and check your Airtable base to confirm the linked record field populated correctly.
Advanced: Cascading linked record dropdowns
A cascading dropdown is where the selection in one field filters the options in another. This is common in forms with hierarchical data.
Example scenario: Your base has three tables. Regions link to Offices, and Offices link to Teams. On a project request form, you want users to select a Region first, then an Office within that region, then a Team within that office.
With Filla, you can build this using conditional logic combined with filtered views.
Approach 1: View-based filtering per region
If you have a manageable number of regions, create one Airtable view per region in your Offices table. Filter each view to show only offices in that region.
In Filla, show the Office field only after the Region field is filled (using conditional logic). Then configure the Office field's filter view based on the Region value.
This works cleanly when regions are fixed. It doesn't scale well if you have dozens of regions.
Approach 2: Use a linked record field with conditional display
A simpler pattern for many cases: show the sub-selection field only when a parent selection has been made. This prevents users from picking an office before they've picked a region, which avoids mismatches.
In Filla's conditional logic settings, set the Office field to display only when the Region field is not empty. Set the Team field to display only when the Office field is not empty.
Users move through the hierarchy naturally. If they change their Region selection, clear the downstream fields and have them re-select.
Approach 3: Single linked record field with compound names
Sometimes the simplest solution is the right one. Instead of cascading dropdowns, create records in your linked table with compound primary fields: "Northeast / Boston Office / Engineering Team". Users search by any part of the string. No cascading logic required.
This only works if the total number of options is manageable (under a few hundred). Once you have thousands of records, search-based selection without hierarchy becomes slow.
FAQ
Why doesn't native Airtable support linked record dropdowns in forms?
Airtable has never given a clear explanation. The feature has been requested for years in the community forum. The current behavior (raw text input) appears to be a product decision, not a technical limitation. Third-party form builders like Filla fill this gap.
Will the linked record options update automatically when I add records in Airtable?
Yes. Because Filla connects directly to your Airtable base, new records appear in the dropdown as soon as they exist in Airtable (and meet the view filter criteria, if you've set one). You don't need to update the form when your data changes.
Can form users see linked record data they shouldn't have access to?
The dropdown shows records that exist in the filtered view. It doesn't expose other fields from those records beyond the display fields you configure. If you have sensitive records, filter them out using an Airtable view before pointing the form field at that view.
What happens if a linked record gets deleted after a user starts filling out the form?
If a record is deleted from Airtable while a user has already selected it in an open form session, the submission will attempt to link to a non-existent record and will fail gracefully. This is an edge case. For most use cases, records don't disappear between form load and submission. If you're concerned about it, use Airtable automations to archive rather than delete records.
Start building forms with proper linked record support
Linked records in forms should work the way they work everywhere else in Airtable: with search, with filtering, with context. They don't in native forms. That's not going to change.
If linked records are important to your data model, and they probably are if you're using Airtable seriously, you need a form builder that handles them correctly.
Filla does. Free plan includes 5 forms with unlimited submissions and full linked record dropdown support.
Build your first linked record form →