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

Please allow accessing headers (for example for authorization check purposes) and raw body (if I don’t know the exact JSON structure in advance) in Automations. ... View more

A small feature request. It would be helpful if Airtable displayed the colour name when hovering over the colour-picker options when building a single/multi-select field, and in the Color Condition options - similarly to how Excel does. This would be a big help for colour-blind builders. Thanks, Chris ... View more

I’ve used Airtable for a long time and I wish it had these two simple features: Ability to reset filters/groups/sorting to a user-defined default for each view. That way I can play around but then reset to the defaults. Right now I just generate a view-only link for myself so I don’t mess up my view and refresh to get back to the default settings. It would be much better though if I could make changes in-base then either reset them or set them as the new default to lock them in. Ability to update all views when I change something. For example, if I add a new column and then resize the column then for all of my other views, that column will be tacked on to the end and will not be resized. It’s a lot of work to go through and fix that column in every view every time I want to make a minor change like resizing or adding a column. Often I just delete all of my views and recreate them, since it’s easier than manually updating them all. Anyone agree? Any workarounds that I’m not realizing? ... 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

Hi Guys, Is there a way to invite users direct to Interface Designer and only have access for that specific Interface Designer? ... 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

May I suggest a very helpful, super simple to implement, feature? Problem: Sorting (ascending order) a single select that has empty values puts all the empties up front. Work around: Reverse the single select options order (put 1st at bottom), but this is a pain. Suggestion: You already have “Alphabetize” in Single or Multi Select, which sorts A-Z. Please enable a 2nd click to then sort Z-A. Voila! Now sort my view Descending and my empties will be at the bottom and my single selects will sort in the view correctly. A better, more intuitive solution might be to provide a switch in Sort dialog: “Sort empties at top/bottom”. ... View more

In our CRM, we have a COMPANY Table and a CONTACT Table (among others). Within each of these tables, we have a CLIENT view and SUPPLIER view. PROBLEM: EXPANDED RECORDS That said, when I expand a record in the Contact Table > Supplier View, I’m inundated with irrelevant Client-Contact-specific fields (ex. ‘Won Projects’) haphazardly stacked at the bottom of the record. It’s become very confusing and bulky for our staff and, in my opinion, it’s probably a big reason so many of us wish we could ‘link bases’; but I won’t dive into that. PROBLEM: EXPANDED LINKED RECORDS Likewise, when I’m in the Company Table > Client View, and I want to access Contact Info for one of our Client companies, I’ll simply click to expand one of the linked records (linked from the Contact Table). In this case, I’m still inundated with Supplier-contact-specific fields, lumped together at the bottom. Ultimately, we need these gone! SOLUTION I’d love for a given record to expand into a Default Expanded View Preference (i.e. with default visible fields) that was specified during the creation of this contact/record (i.e. every time I add a new record to the Contact Table, I can select what type of record it is [“Client” vs "Supplier]; in turn, instructing AirTable on which fields are relevant to that record). The result, in the above example of expanded linked records — our entire sales team will always see this expanded linked record as a “Client”-specific record, per the records’ system-wide default expanded view setting. DEFAULT VIEW & CUSTOM VIEW PREFERENCE But then (hear me out!), once any given record is expanded, I’d like the option to specify, from a dropdown within that expanded record view, how I’d personally prefer to view that contact/record going forward. For example, the Default View for a given Contact record could’ve been set to “Client” when it was created; but, depending on my department and the info I typically need, I can now select an alternate ‘view preference’ from the expanded record drop-down (ex. maybe I choose “Client Finance Data” or “Client Holiday Gift Info”). Once I’ve selected a new expanded ‘view preference’, AirTable would remember this selection as my new personal default for that specific contact/record. The result — anytime the record is expanded by ME, I’ll only see the info that’s relevant to my work. If I need additional info/fields in the future, I can always change my “view preference” with the dropdown. Again, I think this feature would help to calm people’s consistent request to link bases. I do believe all data can be kept in 1 base, and I’d prefer it that way; but we need more features to help us hide things that we don’t want to see. ... View more