Filter records by field that is a lookup

[rmc1977]

Hi Everyone,

I have base called PROJECTS with two tables:   

1.  "Sync" that syncs all the values from another base called CLIENT MASTER.   

2. "Projects" which is a list of projects.  Each record in "Project" can only have one client.

When a new record is created in the "Project" table,  the user selects a linked client record from "Sync"  then there are lookup fields that auto-populate with fields like Account Executive, Partner, and other client information.

So far that works just fine.

I have created an interface with a list of records from the "Project" table.   I want to set a filter on the interface so that the only records displayed for the user are the ones where "Account Executive"= Current User.

However, when I create the filter,  "Current User" is not an option.    Strangely, when I create another test field in the Projects table called "Test User" (User field type), I AM able to use that field as a filter and "Current User" is an option.

Is the trouble I am having because I am trying to filter the interface by a Lookup value?

Any suggestions on how I can achieve a filter so that Account Executives using the Projects interface only see the projects they are assigned to?

[ScottWorld]

Interfaces can only filter for the current user on "user fields" or "email fields", so you would need to lookup either a "user field" or an "email field".

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

[TheTimeSavingCo · Accepted solution]

Hmm, as a datapoint, I just tried recreating your setup like so:

And in the Interface I was able to use the "Current User" filter:

[rmc1977]

Is your information in the Clients table syncing from another base?

[TheTimeSavingCo]

Yeap! 

[rmc1977]

Thanks... I figured this out.  Seeing that it worked for you made me go back and check the field setup in all of the tables.   One of them in the chain had the user field as type "long text."  Changing it to User fixed the issue.
Appreciate it.