Save the date! Join us on October 16 for our Product Ops launch event. Register here.
Aug 15, 2024 02:01 PM
I have a table called "Main" with a user field named "Employee," which needs to stay editable and as a user-style field. I want to add another column in the same table, "Employees Team Members," which displays all users in the same team as the employee. This new field should be non-editable, similar to a lookup, but must remain in the user-style format.
My goal is to have both the "Employee" and "Employees Team Members" columns as user-style fields so they can be used with the "current user" filter in Airtable's interface Kanban view.
Here’s the setup:
I'm open to creating an additional table to manage the team data but need guidance on how to maintain both fields as user-style columns to be compatible with the "current user" filter feature in the interface. How can I achieve this setup?
Aug 15, 2024 03:10 PM
Hey!
You might want to have a specific table for Users (see example below), where you have each Employee's name on one field, and its user on a different field.
You then want to have to different linked record fields on the Main table, linking to the Users table. One called Employee and one called Employee Team Members. For each of those, you'll have a lookup to fetch the corresponding users respectively.
Under this structure the "user type" field for Employee (lookup) is not editable, but the actual Employee field (linked record) is editable. So the same result would be achieved!
Find a link to the base here. An even better way to structure this would be to have a Teams table.
Let me know if this has been helpful.
Aug 15, 2024 11:04 PM
Does the linked "Teams" table have a "User" type field or the emails of the Airtable users you want to filter by?
If so, I think it's possible you can just use a lookup field to display that "User" type field or the emails from that table, and you should be able to use the "Current user" filter feature, and so your Interface filter would be an "OR" to display either "Employee" is current user, or the lookup field contains current user maybe?