What is the proposed idea/solution? The idea is to allow a user to update a record only through a form (similar to the process of adding a new record). How does is solve the user problems? Currently, a user can update a record instantly by changing data inline or in the Details Page. The standard behavior in the internal apps is that a user has to consciously trigger the update process from a details page. It would help to manage and implement all the updates after submitting a form.  Taking into consideration possible integration with Make or other tools, it can send updated fields to a webhook in one shot. Moreover, it would be nice to use a data option of conditional visibility of elements while updating, the same as inside the Add Record Form. ... View more

What is the proposed idea/solution? Add button/option with the ability to print view/sidesheet/full screen ... How does is solve the user problems? it allows the user to print or download a pdf version of the all information in its current layout in the sidesheet without the cutoffs of trying to print the window. Users can print lists and graphs about that record without leaving the interface. Page designer doesn’t work in the interface and has too many limitations.  ... How was this validated? ... Who is the target audience? Interface users. ... ... View more

What is the proposed idea/solution? An enhancement to the record selector that pops up in an Interface when you click on a Field element for a linked record. Currently it allows you to filter and select one option. I would like the ability to filter and select multiple options, eg by holding down the shift key. How does is solve the user problems? Linked Record fields can be linked to multiple records, however there is no straightforward way to assign multiple records in one shot. The filter allows you to see records that are related by a common part of their name -- it is too bad you have to repeatedly type in the common part of it because you can only select one record at a time.   ... View more

What is the proposed idea/solution? It often makes sense to use a unique id field as the primary field in a database (for example "customer_id"), especially as linking records requires the primary field to be used. When this data is then displayed within an Interface, many of the interface elements will show the primary field in bold at the top of the record, when most end users would wish to see the customer name for example.  How does is solve the user problems? Interfaces would be far more clear if records could be displayed with more control over if or how the primary field is displayed, allowing databases to reserve the primary field for unique data strings. How was this validated? ... Who is the target audience? Interface users. ... View more

What is the proposed idea/solution? To hide the first (main) column of a table in a Grid element. How does it solve user problems? Not all tables' first column is important, especially for tables that mainly connect between linked records. While the first column cannot be hidden on Airtable base tables, it should be possible on the Interface Designer's Grid element. Who is the target audience? Those who use the Grid element on the Interface Designer. ... View more

It would be great if you could do more with buttons in Interfaces. For example, link to a from (with URL parameters) from a button so the user has to enter some data before making the change. Alternatively just a prompt for them to enter data when clicking it! ... View more

Consider having the following in an interface: Timeline element AND Record picker or record review list Request I think it would be very practical, on the timeline element, to have a configurable option that when an element is clicked, it would link with the record picker or record review selected item. Concrete example: I have a list of tasks to reviews and a timeline at the top showing all the due dates for the filtered tasks. Under the timeline is the details for the selected task (from the list). This would allow for direct switch of the details by using either one of the list of tasks or the timeline itself. ... View more

There have been many threads in here over the months to make Airtable more Forms Based (rightly so in my view) - but it occurs to me that a relatively simple start to this would be to build a List / Details type view with a brief (one or two fields) list of records on the left and then details displayed on a form on the right. The user should be able to specify fields to use in both areas. This type of layout was used to very good effect by Microsoft as one of the default layout in their Access Web Apps product (now pretty much defunct) - looking like this: Note - this is a screenshot of an app I built and used to sell on the MS App Store before Access Web Apps was announced as retiring - all the data is demo information and not ‘real’. AWA will be retired this month. How about it Airtable? ... View more

In one of our tables, we use the Button field as a trigger to run a script. We have been using Interfaces as a much cleaner way to enter data for some of our teams, but it seems like you can bring that field into Interfaces but the button is not actually clickable. Is there a workaround for this? Will this be added? Thanks! ... View more