Yes, first you will need to create the Link, then a second field for the Lookup which points to the Sanskrit name in your Yoga Poses table.

Then, every Link you make in Table 2 to an English name (under you Link field/column) will result in the Lookup (second field/column) pulling the Sanskrit name to Table 2.

Is there a video or screenshot that shows this? I am trying to use https://guide.airtable.com/linking-tables/ to do this, but it’s not working.


Here’s a video of what I am trying to do:

My goal is to get the “Mautic Campaigns” cell to show, "LW Test 1"


Thanks!


Josh

can you please clarify if there is a way of automatically linking two fields from two tables based on the Id field – as in similar to database table join with primary and foreign keys ?


what I saw is that I need to select the record manually to link. I would like to automatically pick the record based on the id matching on both tables ? is this possible ?

Let me make sure I have this straight:

1. You have two populated tables in the base.



2. 
   
   eTableA] contains {FieldB}, the value of which corresponds to the primary field in eTableB].



3. You want to enter a value into {TableA::FieldB}, have Airtable locate the record in eTableB] with a matching primary value, and populate {TableA::FieldC} with a value taken from the aforementioned record from eTableB].

No, currently that is not possible.

However, is there any reason your heart is set on entering the same data multiple times? If eTableB] exists, simply make {TableA::FieldB} a linked record field pointing to eTableB]. Then, rather than having to enter redundant data, with the accompanying chance of error, the user simply clicks on the plus sign in the linked record field and selects the appropriate record from eTableB]. This may be done from a scrolling list, or the user may enter however many characters are needed to narrow the list of matching records before selecting the appropriate one. In either case, the process is still less labor-intensive than having to enter matching data in multiple locations. Once a link has been made, lookup or rollup fields are used to populate eTableA] with data from eTableB].

This also works with imported data. That is, if you have a linked record field defined within a table and then use the CSV Import Block to add records, Airtable converts values imported into that field into links to records in another table. (If you are creating the table containing the linked record field through CSV import, initially import the values as a basic data field — for instance, single-line text or numeric. Once the import is complete and the table created, right-click on the field header, select ‘Customize field type,’ and change the field to a linked record field directed at the appropriate table. Airtable will convert the imported values into links.)

Finally, if the field in nTableA] whose value is supposed to match the primary field of fTableB] is a calculated field, it is still possible to create an ealmost] automated link to oTableB]:

1. In addition to the formula field in nTableA], create a new linked record field connected to the appropriate table.



2. After data has been entered or imported into oTableA], select the cells in nTableA] for which links are desired. This may be anywhere from a single record, to a block of records, to an entire column: Click the field in the uppermost of the records to link; scroll to the row containing the lowermost, and, while holding down the Shift key, click in the lowermost field. This selects the uppermost, lowermost, and all intervening fields.



3. Press Ctrl-C to copy the selected fields.



4. Click in the uppermost linked record field. (This should be located in the same record as the uppermost selected field.)



5. Press Ctrl-V. This pastes the copied field values into a matching number of linked record fields, which Airtable subsequently converts into links.

Note that in all of these cases, if a value is entered into {TableA::FieldB} that does not match the primary field of a record in nTableB], a new wTableB] record is created, either by the user selecting ‘+ Create a new record’ at the bottom of the list of sTableB] records or automatically in the case of imported or copy-and-pasted data. Typically, if key-matching is used, the only indication no matching record was found is the fields to be populated with data from the matching record remain empty; it is up to the user to search for records with empty fields; determine this was caused by no matching record having been found (as opposed to the field having been empty in the matching record, as well); and create a new aTableB] record manually.

I realize that was an awfully verbose “No” — but I guess it was actually more of a “No, but…”