What is the proposed idea/solution? Many times your summary bar won't give the "bottom line" of a field that the user is actually after. It only allows the very basics like "Sum", and "Average" but misses a universe of options the user needs. For instance, it can not even give a weighted average by taking into account the values of another field. Adding the option (see below) to customize a view's field summary metric (with a basic formula), will turn your database much more useful. Without being able to give things like a weighted average or calculate anything involving another field makes the ability of your database to give insights quite poor. This will solve that: customizing will allow me to name the metric I'm after, and use a formula to determine what is shows. Like below:     ... ... 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

What is the proposed idea/solution? It seems likely that this is already being developed, but I suggest adding a new feature to the Button interface element (see attached screenshot for expected location) that allows users to apply a record template to the current record. This enhancement would help streamline the process of creating sets of sub-tickets and eliminate the need for cumbersome automation currently in place. How does is solve the user problems? Allows for faster, easier deployment of records in an Interface. Simplifies base administration. How was this validated? ? Who is the target audience? People using Interfaces with a concept of 'sub-tickets' -- probably other use cases. ... View more

Airtable interfaces have totally changed the way we are able to work with our data. Working in the actual bases is becoming more and more an admisitrative task, designing and creating the data architecture as well as all processes working in the background (scripts, automations, extensions). A new type of interface experience This calls for a completely new powerful approach to how interfaces are organised and accessed. We would like end users to sign into their Airtable account and see something like a landing page of our company (workspace). There they are shown the interfaces they can access (permissions). Interfaces from all bases in that workspace. This landing page should have design features, so I can create this experience. A new type of user level? This also could call for a completely new category of users. People who exclusively work with data through interfaces and no longer have any contact with the base in the background. This user level could be divided into two groups: People being able to work with data: create new records, edit data, etc. People only viewing data New pricing modell? With this a whole new pricing modell could be considered. This modell would differentiate between admins, programmers, base editors and end users of which there would probably be more than the former. ... 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? In the Record List Interface, the search field has to be manually cleared by deleting the text. Please add functionality to clear the search field so we can clear it with a single click.   How does is solve the user problems? Fewer keystrokes and easier searching How was this validated? ... Who is the target audience? Anyone using the search bar in Record List Interface   ... View more

1. Interface Shape Elements that can be edited with text Ex: Flow charts 2. Interface Element that displays a calculation. Say I wanted the formula to subtract the value of 2 Number elements in my Dashboard  3. A toggle button that allows you to jump to the top or bottom of a grid view 4. The ability to group records by exact dates Ex: 6th of the current and next month like a bank statement 5. Formulas that reference the previous record Ex: A running balance 6. Automation notifications on the app 7. More robust chart options in Interface Ex: Combo Charts. Say I wanted to show change in SLA vs a constant goal 8. More in depth chart designing Ex: visible data points, data labels, editing the scales, etc. 9. Ability to insert images and blank ,expandable tables in Interfaces ... View more

What is the proposed idea/solution? Give Admins/Creators the ability to adjust the Search Index(or provide multiple indices?) for a record so that when you are linking another record to it, you can more easily find the record you are looking for. ... How does is solve the user problems? Currently, it only uses the record’s primary key as the search term, which sometimes leads me to create a "Search Terms" (or Label) field (formula-type) as the record Key, concatenating other fields to enhance search-ability.  There has to be a better way that doesn’t force hacky behavior like this. ... How was this validated? ... Who is the target audience? Anyone wanting to streamline record linking ... ... View more

What is the proposed idea/solution? We need the ability to make more robust charts in interfaces. How about bringing something like the vegalite extension to interfaces? PLEASE How does it solve the user problems? Basic visualizations like overlaying a line and bar chart can't be done, but vegalite can do things like that and much more. Who is the target audience? Anyone who wants to have robust data visualization in their interface ... View more