Help

Create new table with additional columns from filtered search

Topic Labels: Base design Views
79 2
cancel
Showing results for 
Search instead for 
Did you mean: 
raganrhodes
4 - Data Explorer
4 - Data Explorer

Howdy! 

I have a list of all of my vendor partners, which includes a single select column for the type of vendor. I would like to create another table with a filtered list of my partners of a specific type, web integrators.

raganrhodes_0-1712081816161.png

I would like to do this because I have some additional columns of data that I would like to add and track, but they are only relevant for the web integrators and not relevant for all of the other partner types. The Company Name would be the primary field on both tables.

Ideal, I would be able to create a new table will all my tagged web integrators, such that when I add a new partner to my main list and tag them as a web integrator, they will appear on the new table and I can update the additional columns in the new table. 

What is the best way to achieve this use case?

2 Replies 2

In Airtable, you would do that by creating different "views" within your existing table.

Each view can have its own filters, its own field visibility, its own sorting, its own record coloring, etc.

Here is Airtable's support article on views.

Also, for an even deeper dive into Views, you can check out my free Airtable training course, which you can take for free by signing up for a free 30-day trial with LinkedIn Learning.

p.s. I'm also available for hire as an expert Airtable consultant, if you'd like to work one-on-one with a consultant: Airtable Consulting — ScottWorld

Assuming the "Company" values are unique, create a linked field to that new table you want and then:
1. In the view, click the "Company" field header, selecting the entire column
2. Hit CMD + C
3. Click the field header of the linked field to the new table
4. Hit CMD + V

This'll create one record per unique Company value in the new table

To handle new records, you can have an automation that'll trigger whenever a record enters the view and its action will be to create a record in that other table you mentioned and link it to the triggering record