Skip to main content
Question

Solution for an interface with a multi select record picker

  • February 1, 2026
  • 2 replies
  • 17 views

Forum|alt.badge.img

I have an interface that I use to visualize key data for our clients. There’s a record picker at the top where the client name can be selected. However, we have some clients that fall under a larger parent company, and for those I’d like to aggregate their data into 1 dashboard per parent org.

I tried to create a version of the interface in a dashboard layout, but when I do and create a new group from the Clients table where most of the data is stored, it won’t let me create a filter based on the client name (only other fields in the client table show as options).

Please help! Has anyone else encountered this? Have you figured out solutions/workarounds?

2 replies

Mike_AutomaticN
Forum|alt.badge.img+28

Hey ​@apioscareteam,

I guess you made the “Parent Name” a sinle line text field? Dropdown filters do not support single line text fieds. 

I’d highly suggest you create a new table for Parent Companies. You would then create a linked record field, to link you Clients to Parent Companies. Then on your interface (dashboard) you will be able to use the Parent Companies field as a filter.

Alternatievely, you could use a single select field, but I wold go with the new table option!

Please le tme know if this helps, and feel free to grab a slot if you’d like to go through it together on a 5 mins call.

Mike, Consultant @ Automatic Nation 
YouTube Channel 


Forum|alt.badge.img+3
  • Participating Frequently
  • February 2, 2026

Hello,

This can be a frustrating thing about Dashboards on Interfaces tables.  The main issue that we tend to see is that you are trying to filter the selections by what appears in a Linked Record or record picker.  Airtable Interfaces only allows for filtering by fields directly available in the Dashboard section not picker or lookup fields.



Some things you can do to get around this are to

-“Add a Parent Company field” on the Clients table and filter around that instead. 

-If it is on another table you can create a lookup or for formula field for the Parent Company field on the Clients table if the Parent Company lives in another table. 

-Then use a “Filter Control” based on the Parent Company instead of the client record picker.

You may need to use a separate “reporting table” to roll client data up to the parent level and build out your interface from there if your flow is more complex.