This feature exists.
This is a bit of an issue for third party developers. Airtable itself uses field IDs for most (but not all) of its internal systems. Airtable has put effort into making field IDs more visible, although I feel that they could be even more visible.
Delete history is there for up to seven days. It’s in the trash. If you want more detailed delete history, enterprise audit logs have more details.
Well hot diggity, I feel embarrassed but way more knowledgeable!!! Thank you SO much for this feedback - the View Description I cannot believe I didn’t see! And thank you so much for the info on delete history/audit logs.
Loving a lot of the ideas listed here. Some of them are also on my list! Here are a bunch more!
Apologies for the long list!
Better Undo function.
It would be nice to see a bit more robust Undo function. Right now the Undo is basically what Undo in browser would do. The Airtable app is a Chrome wrapper or electron app or whatever and if it crashes than the Undo function history is gone. If I close the window browser with Airtable, the history is also gone. The Undo is something seems works generally across the whole base. While I know I can see revision history for records, but I can’t see anything similar for revision history for changes to fields. I wish I could just go and select the steps to go back, at least a few of them, last hour or whatever, but see transparently what Undo step is about and be able to Undo whether I close the window or app crashed or not.
That’s more effective than restoring the whole base, which not only takes time but the have to reactivate the Airtable automations and if I have 3rd party bindings like Make automation etc, then I have to fix those as well. That’s a lot of work just to “rewind the tape” a bit to go a few steps backwards.
When the base reaches 499+1 fields (total of 500), attempt to add another fields just crashes Airtable. The reason is because Airtable doesn’t allow going beyond 500 fields. They should have handled it more gracefully than crashing the browser, not only it looks amateurish but confuses the users who are not familiar with the limit because the crash reason is not obvious, there is no information why the session crashed or that the limit of fields has been reached. Just an error message indicating the 501st field can not be added would be user friendlier.
This is not a feature request; this is a bug report. You can report this bug to support@airtable.com. Let’s try to keep this thread clean by posting high-level feature requests that would truly improve customers’ lives on a regular basis when working with Airtable.
Make the box to change the name of the automation longer.
In fact when I select edit, the box gets even shorter:
(Rich) Text Fields that can reference other fields of that same record.
Example:
In the year {year column}, the snowfall was above average.
Adding linked record in field that has been set to a view, actually appends these conditional values to the new linked record.
Not sure if mentioned already, but when I setup a linked record field to only show options of a specific view, then when I make a new record in that linked field it does not automatically give those attributes to show up in that field (it should work similar to when you add a record inside a few where it does automatically gives that records the conditional values for that view)
Yep! Already mailed to Support for this way back 
This is becoming a loooong reading. Are mods still keep track of suggestions? How is this going to help us? Is there a plan to present this somehow to Airtable staff?
Does this board offer an idea exchange type of format that could be integrated like Make for example?
https://www.make.com/en/platform-ideas
No official plan yet. An Airtable engineer said that he was following this thread, but at some point, if it seems like Airtable starts listening to our feedback, I will compile these features into some sort of easy-to-read format.
Hm, okay, so this good news I guess even though if they provided any hints about what could be the turning “point” of interest in our humble suggestions, I am sure you would have already asked us to perform… e.g. sing, dance, crack jokes, etc… no problem. Not even asking for credits or mentions. 
Update Row Action for Google Sheets in Automations.
A must have.
Also the other way around for trigger, now only trigger on new row. Need also on updated row trigger.
Export as CSV to Google Drive action in Automations
Same also would be great to have the other way around for Google Drive as a trigger:
Allow Date Modified to watch a Formula field.
I keep running into this issue over and over since I use Integromat / Make so keeps bumping up. I wish Airtable allows me to watch formula field for changes. Right now Date Modified can only be field directly edited by the user. I can see there are potential negative consequences if a synchronized field field is being used for Data Modified field, but a formula field should be reasonably safe.
What Airtable still lacks today is a control to prevent run-away uncontrolled automations (e.g. circle automations that trigger another automation). That would also prevent risk of automation running wild if the Data Modified field is allowed to watch formula fields.
Make requires a Date Modified field and often times when I need Make to trigger on change in formula field I find myself with doing work-arounds as a result of this restriction.
This would be really nice, especially since automations are able to watch a calculated field for changes.
Watching the underlying editable fields for changes is not a good workaround because the editable fields could change without a resulting change in the formula result.
Easy way to turn ON and OFF all questions or SEVERAL extensions at once. There are often cases we need to do that e.g. when copying a base. Allow us to turn on or off the same way as you can do it in a browser, in chrome or firefox, you can look at the whole extension list and just click click on single page to turn them on or off.
Just a simple addition - On Kanbans add a way to only display specific columns, at least on an interface.
