What is the proposed idea/solution? Other elements, such as Calendar, Timeline, Gallery and Kanban to act as Record Pickers, allowing for records to be clicked within the element, and their subsequent fields to be looked-up and displayed within the interface. Think of the way a Record Picker element behaves, and now apply that behaviour to the other Elements. When you think about a Calendar, it's showing records just like the record picker is showing records, just in a different visual format. Further to these mentioned elements, this same Record Pick behaviour should also be added to Linked Fields and Lookup Fields. How does is solve the user problems? The Record Picker is a very powerful element - but I feel it shouldn't have a monopoly over its specific functionality, and that the other elements such as Calendar etc would all benefit vastly from having this same ability. Who is the target audience? Anyone building and using Interfaces, where multiple tables are in play, typically at 3 levels deep - for example, Project -> (Task Dictionary) -> Task. ... View more

What is the proposed idea/solution? The proposal is to abolish the fees for Interface-only commentor level. Actually, a commentor is a viewer with the possibility to comment, nothing beyond that. No edits, no creation,  no management, etc.   How does is solve the user problems? It would change how companies (like my agency) can communicate with their clients (specifically those who are not active on a daily basis) or external partners over e.g. the workflow, reducing e-mails or calls. Clients (free of fees) can add records to a base via forms and can read them on Interface, but there is no chance to leave a comment. ... View more

What is the proposed idea/solution? At the moment, you cannot readily access the Page Designer through Interface when trying to implement a button. How does is solve the user problems? I would like staff to be able to generate letters in AirTable, but they work out of the Interface, exclusively. How was this validated? ... Who is the target audience? ... ... View more

What is the proposed idea/solution? Providing Interface designers with the ability to allow/disallow the visibility of the field "i" tooltip inside Interfaces. How does is solve the user problems? Currently, we are using text blocks in the UI to explain certain field purposes or possible pitfalls of user selections. You can really clean up an interface and reduce user support questions by providing them with the ability to get further information before making a choice at the exact moment in their workflow that it is appropriate. Blocks of text mean to help a user perform functions really make the entire interface too cluttered to use for experienced users. Some users don't use the system very often so they usually completely forget and need this help but. Maintaining two interfaces with different levels of "Info Help" is not a viable option. From an administration standpoint, this allows for already existing documentation to now serve both database designers and end users at the same time. Future leaning thinking also implies that there could be two fields for "Description" - each with a different set of permissions so that admins can leave themselves complex backend notes for themselves and their teams yet provide more simple descriptions for interface front end users. How was this validated? N/A Who is the target audience? Anyone designing interfaces for themselves or others ... View more

I really need for Kanban to work with a multiselect field the way Timeline works. The ability to group/lane by each option in the multiselect field. Then if there is more than one selection then the card appears in each lane of the selections. I would think that in the split scenario, if a card is selected with options A and B ... then if you grab a card to move it from option A to Option C, it would result in Option B and option C now. If you needed to add a 3rd selection, then you would go into expanded view to edit the selections. We are using this as a todo/workload board. Anything under a team/persons name indicates it's in progress, and we can see what they are working on and when each are due. In some cases we have a task that needs more than one person working on it, but do not want to create new projects for these scenarios. ... View more

What is the proposed idea/solution? Functionality to hide/show comments in a collapsable window within interfaces, specifically the "Record Review" page How does is solve the user problems? Allows users to hide/show what they need to see. Provides more real estate on the window if comments aren't relevant at that point in time. How was this validated? Many clients have inquired about this feature. Who is the target audience? Everyone who uses Interfaces and turns on the Comments feature     ... 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

In Interface, user can only choose a value that already exists in a single select field. In some use-cases, I should be able to add a new value (as it exists when creating from the "Data" interface) It would be nice to have this option enable or not in the field parameters, when configuring the form in Interface. ... View more

What is the proposed idea/solution? Allow users to assign different detail pages based on conditions. When a user expands a record from an interface, allow users to change which details page opens based on conditions of the expanded record. Setting the conditions could work using a UI similar to the one conditional coloring uses. What is the problem? There are many instances where I have records that share 90% of the same info, but based on some differences - such as Type or Status, need to be interacted with differently. For example, for my business we track furnishings and fixtures we refer to as "Items" for architectural projects. We need to ensure that certain pieces of information are recorded for each Item, but what pieces of information we need varies based on the Type of Item. There are so many different kinds of information that we need to record that we have as many as 120 different fields in our Items Table. ideally, we could show only those fields that apply based on a condition, in this case, the "Type" Field. I.E. If an item is of the "Plumbing" Type we want to see fields like "Fitting Diameter" and "Finish", but for an Item of the "Lighting" Type we would want to see fields such as "Input Voltage" or "Socket Type". Ideally we would be able to see all of the Items in one list, and simply have a different detail page open based on things like Phase or Type. At the moment, the only way to do this is to create a different interface page for each type of Item. This approach does not suit the way we need to organize the Items (Typically by Room), and we need to be able to see all the Items in one Grid or List, but be able to open a different Record Detail Page based on the "Type" Field. How does is solve the user's problems? In the attached images I included a simplified example of a Grocery Order Table. The Orders have different Types, and for each Type I created a Details Page that shows only the relevant fields based on that type. ( I am not a Grocer so forgive my goofy and incorrect examples of data) In the mock Interface Editor UI I made, users create different Record Detail Pages the same way they do now. They can then select an option for Conditional Detail Pages that functions exactly the same way that conditional color works: Users can add Detail Pages they want to open under specific conditions, assign those conditions to each Details Page, and specify their priority order and defaults. When a user clicks on a given record in an interface, which Record Detail Page opens is then dependent on the conditions assigned above. Other Notes: There are situations I have come across where this change would allow me to remove complex linked table set-ups that rely on automations to maintain and create links between records. I have one base where this change would remove around 200 automation runs per day, and significantly reduce the complexity of the base. Conclusion: Adding this feature would make a massive difference to Airtable's overall usability for my company, and would enable a wide variety of new use-cases that otherwise depend on more complex base structures. ... View more