What is the proposed idea/solution? Add setting ability to sort linked records in the item details view in interfaces (perhaps in the Appearances section?). How does is solve the user problems? Allows users to present information in a coherent way based on the decided sort function.   ... View more

What is the proposed idea/solution? Add the ability to embed a custom image into a dashboard. Add the ability to embed a custom image into an interface. Add the ability to add a custom image to a base instead of the base name. How does is solve the user problems? Adds in branding and personalization for the company/ team using Airtable. Allows teams to recognize the base they are in if they are dealing with more than one company/ team. How was this validated? I am not sure how to answer this. Who is the target audience? All companies, business, teams who want to further personalize their Airtable experience. If someone like myself deals with multiple teams, I want to be sure I am providing a dashboard that reflects the teams branding instead of just choosing a color that closely resembles the branding. ... View more

I'd like to see a formula function for looking up values in linked records, something like: LOOKUP({Linked Record field}, {Field in linked table}) Basically, a two-criteria lookup similar to "INDEX MATCH MATCH" in Excel without needing to import all the fields from the linked table into the current one. Or just a dot/membership operator in SQL databases. Currently, if I want to fetch data from a linked record, I need to use a Lookup field. This is fine if I want to display  the field's values in my table or consistently refer to it in a formula; but if I have multiple fields I want to reference in a single formula, then I would need to add a Lookup field for each of the source fields. This adds an number of extra fields to my base that only serve a single formula field and clutter up my field lists. (Or I would need to do something hacky with the formula, or use scripts/automations.) For example, say I have two tables: Articles and Authors. Articles has fields like Article Author, Article Type, and Article Cost. Authors has fields like Name, Email, and the rate schedule (News Rate, Feature Rate, Review Rate), as below: Articles Article Author – Linked record: Authors Article Type – Single select: News, Feature, Review Article Cost – Formula: ? Authors Name – Short Text Email – Email News Rate – Currency Feature Rate – Currency Review Rate – Currency Articles Written – Linked record: Articles If I want to lookup an author's email address, I can add a Lookup field and it's a good reference to have for every record in my article table. However, for an article's cost, I only want to see the relevant rate from the author's record. Currently, in order to do this, I'd need to add Lookup fields for each rate because the Formula field can only reference fields in the current table: Articles Article Author – Linked record: Authors Article Type – Single select: News, Feature, Review Article Cost – Formula: SWITCH({Article Type}, "News", {News Cost}... News Cost – Lookup: Author.{News Rate} Feature Cost – Lookup: Author.{Feature Rate} Review Cost – Lookup: Author.{Review Rate} But now I have three fields dedicated to this one formula. The fields are of no other use in that particular table and are basically clutter that I have to hide in every view. If a LOOKUP function existed, then I don't need those extra fields, and instead my formula would look something like SWITCH({Article Type}, "News", LOOKUP({Article Author}, {News Rate})... This would benefit anyone working with rate cards, inventories, or schedules (or any case where they need to perform a variable-field lookup). Another use case is doing a "deep" lookup, such as getting the country code for a phone number based on a city. Say you have a base with tables Phone Numbers, Cities, Countries; and Phone Numbers are linked to Cities, and Cities are linked to Countries; and {Country Code} is a field within Countries. Because Lookup fields in Airtable only go to one other table (you can't lookup a Linked Record field in another table and get data from that third table), you would have to add a Lookup field to Cities for {Country Code}. ... View more

What is the proposed idea/solution? A built in extension that provides the ability to bulk download attachments.  Filtering which records include and also renaming files based on any column of the table. How does is solve the user problems? Sometimes we need to export the contents of an attachment column. Doing this one by one it’s not efficient at all. Downloading data in csv it’s not enough. How was this validated? ... Who is the target audience? ... ... View more

Airtable finally added this calendar month as a date filter option which is great, however there needs to be a last calendar month instead of just last month. We need to submit every month our expenses from the previous month. So for example today, I need to be able to see all expenses from January (i.e. last calendar month). How it is now if I do last month, it will show me expenses from Jan 14 - Feb 14 which is not useful. ... View more

Please consider adding on/off buttons (checkboxes) to the filters to allow users to toggle individual filters on/off.  Exhausted from creating/deleting/creating/deleting/creating/deleting/creating/deleting/creating filters 🙂  ... View more

So happy that someone finally filled the void left by Dabble DB. One of the features I found most useful there, but can’t seem to do in Airtable, is linking to entries in another Base. Often, one will have multiple bases which handle distinct aspects of a business or project, but in which one piece of data overlaps. Example: A political campaign may want Bases for contacting voters, managing events, and recording donations. Those are distinct domains which need their own Bases, but which could benefit from linking parts of them together. For example, it would be great to link donations to the event they occurred at, or voters to donations, or record who attended each event. In Airtable at present one has to either cram all of those bases into one, or foregoe the linkage which makes this software so great. It may seem like a small thing, but once you can link bases, the sky is really the limit. ... View more

What is the proposed idea/solution? New Comment automation trigger with conditional logic Add actions to list, create, delete and update records On a JavaScript record object, add methods to list, create, delete and update comments ... How does is solve the user problems? Automation triggered by new comments could be used at the user's discretion. One example is to send a message/notification to a third-party service like Microsoft Teams. The ability to create comments from automations/scripting could be used at the user's discretion. One example is to leave a comment (as an automations user) if a record didn't meet certain conditions. The current method requires: Generate an access token with data.recordComments:read and/or data.recordComments:write scope Add a Script action to an automation Craft a fetch request for each comment operation and exposing the access token Would be much simpler to create an instance of a record object and use a method like:    record.createComment() record.deleteComment() record.updateComment() record.listComments()   ... Who is the target audience? All users ... ... View more

What is the proposed idea/solution? It would be very helpful if we could simultaneously meet multiple conditions in an automation. How does is solve the user problems? We often send out Emails to users via automations. The content depends on a set of parameters. At the moment we need to build endless combinations of conditions in order to work with the existing hierarchy of how the conditions are executed. As soon as the first condition is met, all other possibilities are no longer looked at by the automation. Looking at all conditions and executing all conditions that are met would totally liberate the way we need to use automations. ... View more