We’d like the ability to hide a given field across the board, in all user views. Such fields are usually elements of complicated multi-field formulas, and require no UI once configured. Such fields should only be accessible in a “Master Data” view. The “Master Data” view would be accessible to Creators only, and would not allow for any hidden fields or filtering. ... View more

I’ve seen requests to have specify a color for linked records, but I’d like to request a feature where the linked item actually gets its color from the linked table. Example: I have tasks with a “completed” field in one table. I created a nice color coding in that table to see at a glance, what’s in progress or done. I then link to these tasks from another table. But there, I only see a long list of grey boxes that don’t give me any information other than their name. To see which of these linked tasks are actually finished, I need to click every one of them and open the detail window. Imagine I could specify that the boxes should inherit the color from a view of that linked table. In the column config dialog, I pick the view the color should come from and voila. At a glance, I see what tasks are done, in progress, not started, without changing tables or clicking into every one. ... View more

Airtable Automation Action: Send API/Webhook Request NOTE: Yes, this can be done via the ‘Run Script’ action, but having a structured input would be helpful to the average end user. Options Method: GET / POST URL Headers Parameters Authentication ... View more

When querying records in the scripting extension, it is required that the fields are explicitly defined as a list of strings or added via something like {fields:table.fields} as a parameter to selectRecordsAsync. While both methods work fine, the user is left to either type out a list of the field names/ids that will be used within the script/automation or select all the fields wtihin the table, there is no inbetween (that I’m aware of). If there were a way to specify fields based on what is hidden/shown in a view, the querying process would be much improved. Ex. const table = base.getTable("Table"); const view = table.getView("View"); const query = await view.selectRecordsAsync({fields: view.fields}); ... View more

I feel this should be an option (toggle) on Last Modified Time fields. Like “Modify time when lookup fields change”. Something like that. How does it work right now? Currently when a lookup field changes, last modified time fields don’t change on the linked record. This makes sense since you’re not actually changing the record. How would this be even better? Add a toggle to also update LMT fields when lookup fields change. There are use cases with automations and above all syncing and updating with zapier that you could want to trigger a modified field. There are workarounds on this. I usually do it with automations in airtable. For example bringing the Last modified time from the linked record as a lookup field, and then using a function with DATETIME_DIFF to check for differences. Whenever there’s a difference, you trigger a small change on any of the other cells. But that seems overkill (three new cells just to perform this check). I think a toggle would solve a lot and be a lot cleaner. Thanks for your work guys! ... View more

I have a feature request - to be able to have variable weight of font within a text box. This would allow me to have something like First Name: {First Name} Within the block. I use a mixture of static text and field variables and I would like to differentiate so the text flows nicely on the page and not have to move multiple pieces of information to make a page flow properly. Thanks! ... View more

What I would like to see is some visibility into Airtable’s development roadmap. It would be nice to see what features are on the fast-track, that are actively being worked on, what features are on the mid-range schedule, and what features are still in planning or are long-term. Or perhaps what features are 1-6 months out, 7-12 months out, 12+ months out. I would understand having caveats listed knowing that things change and that items get added or removed on the fly, or that sometimes things take a lot longer than expected to work out all the bugs. But there does seem to be a few feature requests that customers feel are extremely important and there is no sense as to when they will be available - 6 months?, 3 years?, we just don’t know? I certainly know there can be extreme complexities to adding features to a front-end controlled relational DB engine so long timelines are expected, but being completely in the dark is frustrating. I have enjoyed using Airtable for the short time I’ve been here, but without any insight into the future I may have to bail at some point. ... View more

19 July 2022 Please, I love Airtable but the simple notifications are not cutting it for a busy team. We need much more control: an integration of notifications for Comments and @mention, notification control in automations, notifications in Interfaces (we are stuck using Interfaces until this happens) have a goal of notifications serving teams IN AIRTABLE without sending email or Slack or whatever, simply being able to isolate records with outstanding notifications of any kind for the current user in a search would be bliss, and more. I’m sure you get it already but this is as important for team collaboration as being able to do the things Airtable does well: shape the data, make effective interfaces, etc, etc. ... View more

Hello ! Simple feature with great value : it would be nice to have a Description field in the Automations, similar to the Description in Tables, Columns, or Apps, ... View more