Hey team! We created an interface for our orders, and have one page that is "view only" and another that is editable.  I placed an "Edit" button at the top of the view-only interface that opens the editable one.  However, it doesn't stay on the current record ID when doing so, and instead goes back to the record at the top of the list.  It would be nice if on this menu, there was an option to "Stay on current record" for buttons. This would enable us to more smoothly go through our workflow when processing orders, and I'm sure others would find other uses for it as well.   ... View more

For example my column name is "First_Name" but in my form interface it is "First Name".  But the form error shows the Column name which is not intended to be external facing, where as the form names are external facing. Screenshot:   ... View more

What is the proposed idea/solution? It would be helpful to create formula fields within an Airtable Interface that are independent of the underlying data table.  How does is solve the user problems? For our account managers, we wanted to create a profit calculator in their dedicated interface. Doing so involves using our underlying data from the source table to create several new formula fields. To accomplish this we had to add multiple columns to our underlying data table, which are only useful in the context of this profit calculator and aren't related to the rest of the data in that table. The ability to create customer formula fields within an Airtable Interface that don't impact the underlying data tables and require the creation of new columns would help de-clutter our data tables.  How was this validated? ... Who is the target audience? Account Managers, sales reps, or anyone else who uses interfaces to manipulate underlying data ... ... View more

'List' type objects need a way to export the data (should we choose to allow it).  The workaround now is to create a shared view with the same data and filters, but to protect this data the only option is password.  Since interfaces require log-ins and shared access, this protection is inherent.  If we wish to allow users to export the data there should be a button for this available on the list views.  ... View more

It would be useful to be able to choose to open a complete form when enabling the addition of inline tasks in the Kanban view. Now only the data that can be viewed in the view is displayed. ... View more

It would be useful to have the "Add/delete records inline" option split into two options: Add records inline and delete records inline. There are scenarios where it is convenient to be able to delete records but we would like to limit inline addition. ... View more

I am creating an Interface Form and I have a long submission message. The text does not wrap until it hits the edge of the page, which looks bad and is hard to read on a wide screen. Ideally it would automatically wrap at a reasonable reading width with nice justified text.   As a workaround, I added line breaks. But this required a lot of back-and-forth to get it to look good and it was annoying that I had to submit my form every time I wanted to test a change. A quicker way to preview the submission message would be very convenient. Here's what I ended up with. Not the prettiest but it'll do.       ... View more

I have a table with many, many fields (150+).  Not all of these fields need to be populated.  In fact, most of them are sparsely populated based on conditions present in other fields. It would be awesome if in GRID VIEW there were a way to selectively "gray out" field values based on a formula (unique formulas per field would be ideal).  That way, users could visually know when to "skip" a certain field and focus their attention on others. I need this functionality specifically in GRID VIEW, because my users do a lot of visual comparisons between ADJACENT records -- and there's no easy way to do this visual comparison in any other view types currently. ... View more

What is the proposed idea/solution? Create a way for users to add a chart element to interface record layouts, similar to currently available elements for pages. This would be an especially helpful feature if the layout version was capable of displaying a record summary. For example: I have a table of people with fields for how much they've contributed in a year (one field per year). A chart in their record could display each of the values as a trendline. Values could easily be stored as linked records in a separate table if it makes grouping them together for summary easier. How does is solve the user problems? This feature would make summary data available at-a-glance on the record level, expanding upon Interfaces existing able to ease access to base and table-wide information. Who is the target audience? Any user relying on Airtable to store and review customer data, particularly those needing to review individual trends over time. ... ... View more