Skip to main content
Solved

Create same record in two tabs

  • October 30, 2024
  • 3 replies
  • 32 views
M
Forum|alt.badge.img+7


Hi Everyone, 

I have a base with 3 different tabs. Fist Tab is a Project General where I'm adding new projects. The second Tab is for a specific task (Scanning) and we are creating rows by floors, and it is linked with a specific project. The third tab is for the last task (Modeling), it needs to be tracked by floor as well. I would like to have an automation when a new floor is created in the Scanning tab, create a new record in the modeling tab with the same name, and if it is possible with the same project already linked. 

Could someone help me with that? 

Thanks!!!

Best answer by DisraeliGears01

Easy enough with Automations.

Create one with a "When record matches conditions" trigger in your Scanning table, set to fire when "Floor" and "Project Name" are not empty. Then make a Create Record action in your Modeling Table, with your field settings as Name= "Name" (from Scanning), Project Name= "Project Name" (from Scanning). You can also link the Scanning and Modeling records together recursively (I'd use the passed through Airtable record ID).

3 replies

DisraeliGears01
Forum|alt.badge.img+21
  • DisraeliGears01
  • Genius
  • 301 replies
  • Answer
  • October 30, 2024

Easy enough with Automations.

Create one with a "When record matches conditions" trigger in your Scanning table, set to fire when "Floor" and "Project Name" are not empty. Then make a Create Record action in your Modeling Table, with your field settings as Name= "Name" (from Scanning), Project Name= "Project Name" (from Scanning). You can also link the Scanning and Modeling records together recursively (I'd use the passed through Airtable record ID).

M
Forum|alt.badge.img+7
  • Martin952
  • Author
  • New Participant
  • 3 replies
  • October 31, 2024

Thanks @DisraeliGears01 it was easier than I thought!!! Could you explain how to use "You can also link the Scanning and Modeling records together recursively (I'd use the passed through Airtable record ID)." Im lost with the records ID

DisraeliGears01
Forum|alt.badge.img+21

It's easiest to understand with previews and test steps being modeled. Recursively also might not have been the best word for what I mean.? Regardless...

Basically you can also make it link the newly created modeling record to the scanning record that triggered it's creation. All records inherently have a RecordID, even if it's not visually expressed in your base. When AT automations run, behind the scenes they use that RecordID, and you can use it to specify records. So in this automation (pic included) after the trigger is launched, it creates the new record by copying the name from the Floor field in Scanning, it creates the same project link as the scan record, and then it link the modelling record to it's scan record by RecordID. It's really just if you want to directly link Scanning-->Modeling 


Terms & ConditionsAccessibility statement