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

What is the proposed idea/solution? Price per user rather than per Workspace - Or allow better organization, folders, etc within a Workspace.  We pay more per user on a Pro plan than we do for our CRM.  Yet if we want to collaborate with external parties we need to move the base to a free workspace due to the sharing limitations.  We are a small company and purchased pro for everyone - yet it is becoming a mess.  We cannot even segment visibility of bases within the workspace from some users, since everyone needs to be a pro for that workspace.   Enterprise is outlandishly expensive for small organizations.  We are willing to pay for the service, but the limits even on a pro plan are limiting our use and commitment to the product. How does is solve the user problems? ... How was this validated? ... Who is the target audience? ... ... View more

I know this has been posted many times before, but we need a real solution to allow for grouping by multi-select fields in a way that makes all records associated with at least that value shown in the value grouping.  Yes, this might result in one record appearing multiple times in a grid view. Yes, that is desirable.  Notion users know that this is much more intuitive and user-friendly than the way Airtable handles this behavior.  --- Here's a real example for us: We do project planning in Airtable across quarters. Projects may span multiple quarters (multi-select field). There is no way to view all projects grouped by quarter where all Q1 projects are collected in a single group!  As a designer, it boggles my mind that it behaves this way...   ... View more

What is the proposed idea/solution? Currently, there's no way for an element (i.e. a Kanban element) to be connected to multiple filter elements. This would be useful for example if a user needs to create an interface with multiple sections. The interface having a main general filter affecting all the elements in each section, and each section containing secondary particular filter elements. The connection here would be "AND" between the filter elements. How does is solve the user problems? This would allow making the interface much simpler, instead of repeating the same filter elements over and over again across all the filter elements of the page, a general filter would be set at the beginning of the interface and the following optional/secondary filters would be left for each section across the interface. Currently the interfaces with this approach are super repetitive and a user needs to apply a single filter multiple times.   How was this validated? ... Who is the target audience? ... ... View more

What is the proposed idea/solution? Allow Fields in Kanban Cards (either for Views or Interfaces) to be multi-line. See how a Trello Card looks like: See how packed the tags are and how much information is contained in 3 lines. Now see the same in Airtable for a Kanban Interface: See how the Tags Field is cut-off, not letting the user to see all the corresponding Tags. This issue applies to other potentially long fields such as Text or Formulas containing a concatenated text string. How does is solve the user problems? Currently, the only field type that supports multi-line is the Long Text. However, since the cards are small, any field with more than 4 words get cut off, and a user needs to get into the card details to understand what the card is about. How was this validated? ... Who is the target audience? Trello users trying to switch to Airtable ... View more

Have you ever found yourself asking these questions? “Why did I create this field?” “Why do have a ‘Name - Status’ formula in this field?” “Can I delete this field?” "What’ll break if I delete this field? It’d be nice if we could see where our fields are being used. Perhaps a third tab in the “Customize Field Tab” area, right next to “Formatting.” Where it would list dependent fields! BOOM. DO IT! 🙂 ... View more

In working with the Organization Chart Block, it would be really neat if we could just embed the block dashboard view instead of having to have the entire base embedded in a website. It would help our site look a lot cleaner. Thanks! ... View more

Snapshots would be much much more useful it they could be named (like Google Drive does) and “pinned” so that they wouldn’t be overwritten by automatic snapshots. ... View more

I’d love to be able to create a column, that when linked to a URL column for Instagram, Twitter or Facebook, rolled-up the follower-count, and updated live. This would be HUGE for everyone using Airtable to track social media. In our case, we’re leveraging Gallery View to build a casting base, but we need to be able to sort my total influence. Right now, we’re entering the follower-counts manually, and they grow stale the second you hit return. ... View more