I’m having a bit of trouble managing complex bases that heavily rely on linked records across tables. I’m finding that, as I develop a project or a record keeping methodology I tend to change field names to help myself and my teams keep information conceptually well defined. This becomes problematic when a renamed field is a linked-record field type. Because the newly edited field names from one table do not update the linked-record field name in the related record/table, that other table can quickly become very confusing and difficult to relate to.
Of course this can be corrected by carefully managing names across tables manually - when one field name is changed, the editor carefully changes all linked-record references to it across the base - but it is starting to become a whack-a-mole problem for me.
Can anyone relate to this problem and/or provide insights on how to get past it?
Would it be a reasonable feature request that the names of linked-record fields are inextricably linked across a table either by default or by selection?