Hi, It would make my life so much simpler if we could write functions to pre-fill default values for fields. At the moment, I have many columns in pairs, one column with a computed “default” value, and the other with an editable value. (When the values are equal, I make the computed field display “…”) It works but it makes my rows really long! -Donald ... View more

My team and I would love to work asynchronously on one airtable but when we leave each other comments on records the number stays there forever so we have no way of keeping track of what still needs to be discussed (you can erase your comments but not others and that way you erased the convo!). I’d like a way to get rid of the number shown on the record please. ... View more

Hello! We have a total view of run Automation in the Usage section of the Billing page. But it’s for all table, and all automation together. I would really like it to be more specific. To my need, I would like it to be shown in the Automation tab, for each automation. The number of runs executed so far for the period. It would allow us to monitor which automation are consuming most of the limit as well as seeing if some automation are running more than expected, etc, etc. The total for each table should also been available for the same reason! The limit is pretty low, it would be very useful to see where it is spent! Thank you 🙂 ... View more

These posts are asking about a feature similar to the “filterByFormula” in the standard API, to programmatically filter record selection.   Can table.selectRecordsAsync() query a table or view? Scripting app I see that you can get all records from a table or view - and even sort them. But what if you want a subset - for example all those records connected to another record? It’s not always possible or desirable to create views for this type of thing?   More efficient way to query records? Scripting app Is there a way to retrieve specific records without iterating through all the results of a table using table.selectRecordsAsync() or view.selectRecordsAsync()? Something like SELECT / WHERE queries in SQL? Or in AirTable terms, a Filter? This would be far more efficient than having to iterate through returned records checking for the records I’m interested in… My request is slightly different and I think falls into the “interactive” idea behind the scripting block: session.selectedRecords() . The idea Each record can be selected with a checkbox on the far left-hand side of the row, or all records can be selected from the box at the top. The UI allows users to “Send” or “Delete” the selected records from the base when right-clicking after selection. Providing a scripting block some way to detect which records are selected could help with more granular use-cases. For example, the user wants to update 4 records in “GroupX” and 2 records in “GroupY”. Right now, there are easy ways to filter records matching “GroupX” OR “GroupY” but not a mix (absent other algorithms for detecting the desired records). Potential issues One implementation issue that comes to mind is when does this selection get stored. If a user runs a scripting block with “N” records selected, provides some information via an input.textAsync() and deselects some records before submitting the text, does the script use the selected records at script start or at moment of execution? What do others think? And anyone from Airtable, can you give hints if this might be in the works (or any other session variables for that matter)? ... View more

Is it possible to import fonts natively or through a workaround for the page designer block? Looks like it’s just google fonts? Thanks for any insight. ... View more

It would be useful to have a “Button” field type that you could use to trigger an action (e.g., perform a calculation, run a Block, trigger a Zapier Zap, run a script, run small automations, etc.). Even though some of this functionality can currently be hacked-together using other fields like checkboxes in conjunction with Views and Zaps, this is something that has to be explained ad nauseam to new users. So, instead of having a “Submit” checkbox in a workflow that can accidentally ticked, having a distinct “Submit” button would be much, much more clear to novice/infrequent users. This is a feature currently offered by Coda. help.coda.io Overview of Buttons Learn how buttons can create workflows and an app-like experience in your doc ... View more

Why hasn’t this been implemented yet? This should be a no-brainer. Allow users to reorder automations manually. Sort Automations by Name Sort Automations by Last Updated Sort Automations by Last Ran Sort Automations by HIGHEST NUMBER OF ERRORS (within a 7 day period) Sort Automations by HIGHEST NUMBER OF EXECUTIONS (within a 7 day period) Sort Automations by LARGEST NUMBER OF RECORDS EVALUATED (within a 7 day period) Sort Automations by Created Date Sort Automations by WHICH USER CREATED THEM … I’m sure others can add to this list … (facepalm) ... View more

I would suggest that form submissions that include attachments should also be able to (optionally) include those attachments in the automated emails that get sent out. ... View more

Grouped records and the summary bar - functionality here is great, but the only way to sort the grouped records is by the order of the grouped by field options. I’d like to be able to sort by the numerica values in the summary bar (e.g. revenue or # of records) ... View more