Re: when record created create vlookup in other base

462 0
Showing results for 
Search instead for 
Did you mean: 
5 - Automation Enthusiast
5 - Automation Enthusiast


I want to create an automation that when I create record in table A it automatically will create the same record as vlookup in table B.
so if i update the record in table A it will reflect the record in table B.

is it possible to do?


5 Replies 5

In Airtable, you accomplish that by creating different VIEWS in the same table (instead of creating different tables).

You can learn more about views in Airtable’s support articles here.

Additionally, if you’d like an extremely deep dive into views, you can take my free Airtable training course, which you can take for free by signing up for a free 30-day trial with LinkedIn Learning.

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 


Its not related to views.

Please, read what I wrote in the post


I read what you wrote, which is why I recommended views to you. It is not proper database structure to have the exact same record appear across separate tables. But if you do want to have the exact same record appear across separate tables (which I do not recommend), then you would need to create an automation for that.

I work in a property management company. I have a table for regular tasks and another table for faults that need to be repaired in the properties. Every time there's a new fault, I want it to create a task as well. Do you think I should create one table and call it 'faults/tasks' or continue with the two separate tables?

Community Manager
Community Manager

I agree with Scott based on how you described it.  A fault is a type of task that needs to be done.  

if you had a separate table with people who get assigned the tasks you could use linked records to link the assignee to the task.  

you have another post that says you want to create the same data in another table which is not good practice.