There is a BASE / Table / bunch of fields.
There is web app using API, which neatly makes a form for users to change their details, not just create as Airtable native forms.
Everything works perfectly, until team member changes the field name.
I know you can use serial name “fld123ABC456”, but it involves creating another object to hold pairs of serial names and human readable name. Code is also much cleaner with field names. rawContacts[xyz].fields[“Some Field Name”] reads much better than rawContacts[xyz].fields.fld123ABC456
Question: is there a native way to find who and when made a field name change.
Also how the change was made old name → new name and old type → new type
I have been asking Airtable, as enterprise user for years now, to implement admin layer on field definitions, so that very few people can make these devastating changes.
In the meantime, is there a log of these changes natively?
Or does it have to be a hack of either manually definin
There is a BASE / Table / bunch of fields.
There is web app using API, which neatly makes a form for users to change their details, not just create as Airtable native forms.
Everything works perfectly, until team member changes the field name.
I know you can use serial name “fld123ABC456”, but it involves creating another object to hold pairs of serial names and human readable name. Code is also much cleaner with field names. rawContacts[xyz].fields[“Some Field Name”] reads much better than rawContacts[xyz].fields.fld123ABC456
Question: is there a native way to find who and when made a field name change.
Also how the change was made old name → new name and old type → new type
I have been asking Airtable, as enterprise user for years now, to implement admin layer on field definitions, so that very few people can make these devastating changes.
In the meantime, is there a log of these changes natively?
Or does it have to be a hack of either manually defining variables in code like: const fldContactsSomeFieldName = fields.fld123ABC456
Or interrogating META, keeping a blessed copy on each run, and checking on each run, so that I can flag up: aha, this user, at this time, has changed field name from “OLD” into “NEW”
This should be very basic root implementation on Airtable level, not a massive pain, or a hack workaround as it currently is.
BUT, any help or pointers on how to deal with it now would be greatly appreciated
g variables in cod,e like: const fldContactsSomeFieldName = fields.fld123ABC456
Or interogating META, keeping a blessed copy on each run, and checking on each run, so that I can flag up: aha, this user, at this time, has changed field name from “OLD” into “NEW”
This should be very basic root implementation on Airtable level, not a massive pain and hack workarouns as it currently is.
BUT, any help or pointers on how to deal with it now would be greatly appreciated
