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

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? for better accessibility -  please label the colours with text - when hovering over in the base design How does is solve the user problems? 1 in 12 men and 1 in 200 women have some form of colour blindness - or colour visual deficiency.  This means that distinguishing many of the colours in airtable is difficult.  Giving bases different colours is great as this is both a visual cue when you use multiple bases and interfaces - and in communicating with the teams that use them - however when some users aren't clear which colour is which (I am one and i develop tools heavily in the platform) it causes needless friction - for what should be a quick fix How was this validated? please see standard accessibility guidelines for using colours and ensuring those with sight problems can see the tools effectively. Who is the target audience? all users and all users with colour blindness - e.g. disabled providing greater accessibility.   ... View more

What is the proposed idea/solution? The ability to define a condition for an interface field to be visible  How does is solve the user problems? I have a table that includes one record type. However, the table is populated by two different sources that contain different types of information. The current interface page, with all fields visible, looks noisy and can be confusing to internal users. If I had the ability to hide empty fields, it would be a major UI/UX improvement.  How was this validated? It has been requested internally by several users. Who is the target audience? Internal company users. ... 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

What is the proposed idea/solution? If an email field is set to required on a form, the form should not allow the user to submit unless there is a valid (properly formatted) email address entered into the field. How does is solve the user problems? It allows form users to fix issues before submitting a form with invalid data. It helps the form owner ensure that the incoming data is correct. It makes it more likely that the form owner will be able to contact form users and e.g. send confirmation emails. How was this validated? People are expressing their frustration about the lack of this issue on a number of different threads in the Airtable forums. Who is the target audience? People creating sign-up forms or any form where the form submitter might need to be contacted as a result of submitting their info.  ... 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

Within a base, when a user adds a new record from mobile, they have an option with an attachment field of taking a photo with their device (camera icon), selecting a photo from their device (landscape icon), or three dots to upload a file.  To take or add a photo, it's one click. On an interface, when users are adding a record through a form, they don't have this option - attachment field shows a down-arrow icon with "Drop files here or browse".  They then have to do one click on that button, then a click on the 3 lines menu, then click on Take photo, then click on "Click to record audio, video, or pick file", then "Photo Library" or "Take Photo or Video" That's 5 clicks (taps on mobile).  I've already contacted Airtable directly about this, in November, and they said they don't have a timeline for improving this. Maybe a few votes here would help? ... View more