Button field in table can be used to run a script but not an automation. Button in interface detailed view can be used to run an automation but not a script. Besides, these buttons cannot be displayed on record lists. Could Button field be used to start an automation (the same way interface button does)? It could be very useful to have the same button, launching the same automation displayed in different interfaces and in the table views. And also having the button available in lists views. My "hacky" workaround for now, is creating a checkbox field and an automation that runs when the checkbox is checked (and unselect itself at the end). Thanks! ... View more

I have some cells that have a large amount of text information. I would like to see the expanded cell view provide a resizable versus a fixed size panel to allow more of the content to be visible, primarily to increase the width of the panel.  ... View more

Hi all! I have a ton of automations that are simply "Tag with ___ form" where the automation runs if a form is submitted. Basically just to keep track of various forms that we have and where they are coming from. Makes it easier to sort the data. Anyways, my idea is to have some of the various triggers for the automation, also trigger for the conditional logic. In a dream world it would look something like this... New Record Created --> IF (1 Form, Tag with "1", If (2 Form, Tag with "2"..) and so on.... With the limit of 45 automations, I am maxed out when 20 of them are just this. Would also clean up my interface big time. ... View more

While it's possible to autofill a "User" field type using the "Current User" that's logged into an Interface, it is not possible to auto-link a Linked Record using the currently logged in user.  Use case: We have a custom table of our users that contains a number of fields including the user's email address. We would like to have the option to autofill (set the default value) of a linked record to the current user that's creating a new record in an Interface form. Currently the user has to select themselves out of the list and this adds an extra step to creating a new record and introduces opportunity for data entry errors (e.g. mistakenly selecting a similarly named user) Example 1: Shows the properties of a User field where "Current user" is selected as the Default Value Example 2: Shows the properties of a Linked Record where there is no option to use the Current User as a default value to auto select the correct linked record. ... View more

Field names have to be hard-coded into a formula, which makes it so you can't do something like indicate which field name to pull from in a multiselect field. You can only use a switch with hardcoded field names, or use a whole bunch of if statements to make different things happen depending on the multiselect options. I'd love to be able to write like: FIELDS({multi-select that says which fields to return}) and have that return the value of all those fields as an array ... View more

What is the proposed idea/solution? When searching within a view, add a toggle to display only matching records / hide non-matching records How does it solve user problems? Quickly surface matching records within a view to see results "at a glance" instead of jumping to each match. Prevents having to click "next" button repeatedly if there are multiple search term matches within a single record. It's different from setting a filter within a view, because each filter rule only applies to a single field. Who is the target audience? Any user. Interestingly, the mechanism already exists in Airtable, but only in the Calendar and Timeline views. Click the "See records" button, and type in a search term in the sidebar that appears. You will see a filtered list of records, and it searches all fields. It's a feature I use everyday, but I've never seen it mentioned anywhere. ... View more

When you choose a list interface, there is the ability to sort and filter the data.  However, if you choose the list element on blank canvas the there is no ability to sort. Also sorting on grid view in blank canvas would be very helpoful ... View more

What is the proposed idea/solution? The ability for passed query string parameters (key/value pairs) and Headers to be parsed and made available as DATA OUT from the Airtable Automation trigger for When Webhook Received. How does is solve the user problems? The ability to provide query string parameters and Headers separate from POST data. How was this validated? By testing query string parameters and headers being sent as part of the webhook request and those variable values not being present in the received webhook data payload. Who is the target audience? Advanced users of Airtable Automations. ... View more

Do you think this feature will be coming soon please? I see it has been asked a few times & it would absolutely make life easier for many of us.   Thanks ... View more