What is the proposed idea/solution? Similar to Record Details pages, I would like the ability to include additional fields in the dropdown when selecting linked records in interface forms. How does it solve the user problems? I use unique ID's in the primary field, which makes it difficult to identify the appropriate record when selecting from the dropdown in interface forms. The ability to include other fields in the dropdown would allow me to select appropriate records without having another window open to map the ID's to my selection. This has already been implemented in Record Details pages, so I'm hoping it can be added without much issue (pictures attached). It would also save me from having to restructure my database. How was this validated? Everyday use Who is the target audience? Anyone using interface forms ... View more

What is the proposed idea/solution? There is not currently an option to add a generic search bar to a custom interface page.  The only option is to have different filter options How does is solve the user problems? It would give users the abilty to search multiple different fields without having to make sure they are typing matching text in the correct filter option How was this validated? User experience.  The photo attatched shows the custom view that is being used, the reason I do not change it to the prefigured Kanaban view is because there is another view below it that I like having on the same page as the Kanaban view. Who is the target audience? Airtable users ... View more

The issue We're working with list views that show a lot of numeric data for each record. When scrolling down, the header row moves up along with the records, so it immediately disappears from view and all numbers (which don't have any horizontal separator either) become a big blur of numbers.    What is the proposed idea/solution? It would be great if there would be options to: Enable a sticky header Show a subtle vertical line to separate columns Color or otherwise format columns   How does is solve the user problems? I believe any of the above options would greatly help in keeping (large) list views readable. ... View more

Appreciate the ability to bold, italicize, and strike through text in long text fields, and to format as headings, numbered or bulleted lists, etc.  It would be very helpful to be able to highlight text as well, or at least change the color of the text. Change in text color, at least, must be possible as hyperlinked text appears in light blue.  Our particular use case is a shared legal research database, where our long text field is the notes each lawyer takes on each case.  It would be very useful to other researchers to see highlighted passages.  We currently use bold text, but it doesn't really stand out in a helpful way. Thank you.   ... View more

As an Airtable partner, it would be nice to be able to embed external content into Airtable. Although the platform is very flexible, it cannot do everything. By embedding external content, we can build an app interface with infinite possibilities! For example, a Miro board would enable project managers to have a digital whiteboard while leading meetings and taking notes. Hope my feedback makes it to the right person 🙂 ... View more

It would be great if rich text formatting was available in the forms help text. I would be easier to emphasis important points about completing the form properly. ... View more

What is the proposed idea/solution? To be able to group Interface Designer's pages into sections. Additionally, to access them via hover/clicked dropdown or mega menu at the top when the Interface is published. How does it solve user problems? If a user has multiple pages in the Interface Designer, the user should be able to group them into different sections for a cleaner, more organized view. Like data table views having sections on the left, pages should, too, as they act as an alternative to table views. Who is the target audience? Interface Designer users. ... View more

What is the proposed idea/solution? In forms, we are able to capture automatically the account of the person submitting the form (for logged in accounts). Since this is already a feature in place, it would be important to enable this information as a type of filter to be used to manipulate the visibility of subsequent inputs on the form. This way, if user John is submitting the response, we can add a filter down the form so that only if user "john" is submitting the form, the field "A" becomes visible. If user is not "john",  field "A" will not be shown. Note: we are aware that using the manual requester assignment works, but our customers complain that they have to enter it manually, so the improvement is really on using the automated user detection. How does is solve the user problems? Big organizations with multiple teams have different requirements according to the different user groups/teams. This simple feature allows to have better control of the information requested without the need to duplicate a form based on different teams, hence, reducing the maintenance/operational costs. How was this validated? It is a problem that we have in our organization that we're not able to solve as we don't want to duplicate forms. At the moment we mitigate it with training and adding as many "helper texts" to the forms, however, people tend not to read those helper texts more often than we'd like, and our data continues to be corrupted and we need to manually review all the information and cleanup after, when this quick filter would reduce all of that. Who is the target audience? Enterprise customers. ... View more

What is the proposed idea/solution? Summary count of record comments should appear on record lines in a grid in an interface (just like it does when viewing a grid in the base).  How does this solve the user problem? When viewing a grid on an interface, you will know which records have comments. How was this validated? See screenshot.  Who is the target audience? All interface users ... View more