I’ve had the same problem. Particularly on the learning curve of Airtable or even a new application. .If I’d known then what I know now.]

Can you clarify what you mean by this?

Do you mean when you change a table (not a field) name, you’d like all linked record fields that point to it to update?

Thanks Howie! My preference would be that the verbiage in the 'name field’

of the parent table be inherited by linked fields in other tables, rather than the name of the parent table itself.

Could you give a specific example to illustrate here? Thanks!

Sure thing, I’ll keep it simple:

• Suppose I’m building a base to help my team keep track of a kids camp and specifically allergic reactions to food.


• I set up tables for Students, Parents, Foods, Allergies - with a linked field in the allergies table to the foods table - looks good
  
  but then…


• as camp registration goes along it becomes apparent that other types of allergies are going to be a problem - I’ve got kids with dirt allergies, salt-water allergies, horse allergies etc.


• A realistic modification to the base would be to change the name of the ‘Food’ table to ‘Allergen’


• It would be great at this point if the linked field in allergies also updated from ‘Food’ to ‘Allergen’

Howie, to your point, the linked field currently inherits the table name, not the ‘name field’ name. I find that I often enough name the ‘name field’ in a table the same as the table itself but will, sometimes, use the ‘name field’ name as a nuance.

ie Table Name = products ; ‘Name Field’ Name = Product ID #

Thus, my preference for inheriting the ‘name field’ name rather than the table name - though I could certainly be happy with the later too.

Has there been any updates regarding this issue?

I am also having this issue and it’s becoming quite problematic.

My use case:

I have a base that acts as a Property Management System and includes a “Bills” table as well as a “Payments” table. Whenever a payment is recorded, it is then linked to the corresponding Bill from the Bills table.

My Bill’s Primary field is a formula that concatenates the bill number and the bill status (Paid/Open/Outstanding).

The problem i’m having is that when the payment is made against a bill, the name of the bill updates in the Bill table (i.e Bill #30 - PAID), however it is not immediately updated in the Payments table (i sometimes have to quit the Airtable app and reopen it for it to work), and therefore still shows as “Bill #30 - OUTSTANDING” in the payment receipts that i produce (from the Payments table).

Hi, I constantly get frustrated by this too. So many unnecessary steps when I either A) rename a linked record field name, or duplicate a table. In both these scenarios, the linked record field names do not update. The original poster’s description of it being ‘whack-a-mole’ is on point.

I think a simple solution might be for the user to manage the linked record field name from the linked table. So when I change a field name in one table, offer me the ability to also update the linked record field name at the same time.

I’m not sure how you’d deal with duplicating a table with multiple linked record fields at once, but I’m sure your smart minds at Airtable can figure this out!

plus 1 here! seems like such an obvious instinct. I’m setting myself up in Airtable for the first time and, inevitably, my table titles are changing and improving as I build out. Yet for linked records elsewhere, the old table title still appears.

I’m especially having a hard time understanding how this is the default action for Airtable?? It would seem the moment you rename a table, that table’s title would be ‘echoed’ immediately throughout all linked records reference column titles.

Isn’t this the very nature of a database??

The name of a linked record field does not have to match the name of the linked table. In fact, if you have multiple links between the same table, it is best if the fields have names to differentiate the different roles of each linked field. For example, a base could have a bPeople] table and a oProject] table with two linked records between them. One linked record field could hold the {manager} of the project. Another linked record field could hold the {team members} for the project. Note that neither linked record field is named after the table. Changing the name of nPeople] table cannot automatically change the names of the two linked records.