Displaying the field name is useless for so many Gallery views created (and some Kanban views). For example, I don’t need to know that xyz@abc is their “email” or 123.456.7890 is there “phone”. The field names take up far too much space when viewing. ... View more

It would be lovely to have a localization option for the menu language. At least a language-settings file for menu conversion and making it open-source would work. Also community can create lot of language files without any development cost for airtable dev. team.(like wordpress). ... View more

Maybe Zapier has spoiled me, but it would be really nice to get a little more granular detail on our automation runs within our bases/workspaces. Right now, the only way to see any form of metadata re: automations is to go to individual automation’s run history, or to have admin privileges and see how many runs are left in your quota for that exact live billing period/month. I know it’s probably out of scope for this product to offer as granular of detail on these things as Zapier, but being able to look at run quantities from previous months/billing periods, or being able to see which automations are using most of the runs we have allocated would be really really nice from an operational standpoint! ... View more

Would there be anyway you’d consider adding hierarchical single select columns that show different options depending on what is selected in a prior column? For example in one column imagine that you have a list of car manufacturers labelled ‘Make’ Some options in here could be: Audi BMW Ford Volkswagen Then you could have a second single select column called ‘Model’. It would be great if this only showed options related to the first column. So for example if Audi is selected in the first column the options could be: A1 A3 A4 Q3 Q7 Whereas if Volkswagen was selected in the first column the options could be: Beetle Golf Jetta Polo Scirocco ... View more

Im not sure where Airtable is headed. But id be happy to print a customer a nice Paper with all the Products he ordered. I guess id like to make different form views like in Filemaker. ... View more

Automations are such an amazing feature, but a long list of them is unwieldy and makes it very easy to lose track of what is still needed/what exists. Now that there are sections for table views, can we also have sections to organize our list of automations? 😃 Thank you! ... View more

How can Airtable Enterprise Audit Logs be sufficient when they exclude record-level revision histories?  This seems like a MASSIVE oversight.  Am I missing something else here? Original article: https://community.airtable.com/t5/development-apis/reading-revision-history-via-script/td-p/37318 ... View more

It would be great if I could search/filter/sort/group based on comments. Is that an option that I’m just not aware of how to use? ... View more

What is the proposed idea/solution? It would be a game changer when working with hierarchical data for the roll-up field's ARRAYUNIQUE(values) function to return clickable linked record values instead of a comma-separated string when aggregating a linked record field from the source table. Currently, users can only represent one level of a linked record hierarchy as linked record values using lookup fields without risking duplicate linked record values. Multi-selected linked record lookups/roll-ups can lead to confusing UX and fewer group-by options. How does is solve the user problems? This would serve as a workaround for the strange user experience that occurs when using a roll-up field to return a lookup field of multi-selected linked records. This can duplicate of the same record referenced in the roll-up/look-up field. How was this validated? For example: Let's say you have a base with three tables containing linked records in this hierarchy: Dashboards -> Data Sources -> Tables and you want to see a list of Dashboards related to each Table. In Tables, you would normally create a lookup field to a linked record field in Data Sources that is linked to Dashboards. The duplicated values problem occurs when a single table record is linked to multiple data source records, which are also linked to multiple dashboard records. This results in duplicated dashboard records appearing in your lookup field (which creates confusing UX in general, but also makes grouping by this field even more problematic than usual for multi-selects). Who is the target audience? Intermediate base builders, everyone. ... View more