What is the proposed idea/solution? The best yet most annoying feature - is being able to create record straight from a linked column Despite being a feature that sometimes are valuable this feature has created more trouble than anything else. To save tab space we often bunch different items under the same tab. We often use a combination of a locked filter that forces a category into a single select column and thereby split out what should be selectable in different linked columns around the base. This works really well until someone one day realises that they can just add new entries directly from a linked column, but not understanding that they need to issue the right category to the new entry on order to make everything calculate right. This is especially difficult to explain to new people that join our organisation and who has no prior understanding of Airtable and does not understand the underlying structure of how our bases are build. What would be really awesome is the ability to switch off this feature as sometimes it's obviously also a great quick way to add records, but our experience as soon as bases become a little more complicated this feature makes so much trouble. ... How does is solve the user problems? It will enable our users not to make unintended duplicates and records that does not show up in the right linked columns ... How was this validated? Through 22 users and three years of experience ... Who is the target audience? New people you get onboards onto workspaces ...     ... View more

What is the proposed idea/solution? I propose to add a way to organize tables by groups as MS Access does. Currently tables in a base are organized by tabs in a row on the top. I understand that this would be against the Excel-like feeling, where the workbook is organized in sheets, which are actually tabs. But I think MS Access way to organize the tables in groups is much better. This feature would get bases much more organized. For example I would create the following organization for my tables: 1) Entities groups. In each of these groups, I would put just the entities which I am dealing with to model my universe (for example, Student, Tuition for a school or Order, item for a procurement etc.) 2) Lookup Tables. All lookups that cannot be implemented with a single field dropdown list. For example a ROLE table which requires a field like Title, but also a description and maybe other fields like Hourly Rate etc. 3) Many-to-Many associations Tables. For all associations that need to be materialized, because you need to record information for each association. For example, when you assign a parking to a car. The association table is the place where to store the arrival date/time and departure. Table types 2 and 3 are quickly proliferating and pollute the data model led by the tables that deal with pure entities. How does is solve the user problems? I would suggest to implement it as a toggle to the interface, so that the users could switch between the two layouts as they wish. Excel-like (tabs in a row) or Access-like (groups of tabs in a side column).  How was this validated? MS Access actually adopts this way to organize multiple tables. Who is the target audience? Airtable users who works directly with tables and base designer. ... View more

Right now, it looks the Gantt view only supports Finish-to-Start However, I'd like to be able to track Finish-to-Finish The "workaround" to do this would be to further split by deliverable's final step that is actually dependent on the dependency. However, this generates a lot more data and linkage that makes the everything orders more difficult to both manage and digest Start-to-Start is one I can find some use in, too, but Finish-to-Finish is very common Smartsheets is capable of this and summarizes everything well here: https://help.smartsheet.com/articles/765727-enabling-dependencies-using-predecessors  ... View more

A capability that could be extremely relevant for many use cases (i.e., CRM, Project Management, and others) would be the record ID reference in enriched long-text.   Golden does this in a very elegant way (see: https://golden.com/wiki/Microsoft-6GKP), where the description of Microsoft is then linked to another record with structured data.  I imagine a functionality in enriched text that allows you to mention in text for a different record in the same (or different) airtable base.  A clear example is a reference call where you mention that during this reference call, the name of a different company popped up. So the text reads something like: "During the call with a prospective client, the name of record_id:xyx came up. Additionally, record_id:zzy was highly recommended. ". In this case, the record_id:xyx also tracks information on when it was mentioned independently. As well as record_id:zzy both linking to the same reference.  ... View more

My automations would be much easier to maintain if, instead of duplicating an automation for each possible trigger, I could have an action in another automation that triggered it. For example, I would like to send a certain email any time a button is pressed, and also under certain conditions if a form is submitted. Instead of having two identical automations with different triggers, I'd like to have: one automation based on the button press that sends the email (and does nothing else), and a form-triggered automation with a couple actions (unrelated to the email) and a conditional action that triggers the button-press automation to send the email.  ... View more

What is the proposed idea/solution? For bar charts, where we can group field summaries, I propose the ability to limit them to "top x" where x is a custom number field. How does this solve the user problems? If there are a lot of records at play during grouping, then grouping field summaries do not visually work. For example below is a bar chart where: y-axis is the total number of pre-orders x-axis is the release date months the chart shows the sum of different orders it is grouped by brands Ideally, if I want to only see the top 5 brands pre-ordered that month, I would input "top 5" so there would only be five bars, and the rest are "others." Additionally, it would be great to have the groups sorted in ascending or descending order by aggregate or alphabetically. It's best if we can limit it to what we think is aesthetically plausible. How was this validated? Grouping is dependent on the field summary's aggregate. If we can limit lookup fields to last x or first x, I think this should be possible too. Who is the target audience? Interface users. People who like charts. ... View more

What is the proposed idea/solution? In the rollup field settings, we will be able to pull another field as value, rather the rolled up field. How does is solve the user problems? Let's say you have Tasks and Projects tables which are linked.  I want to see in the project table, the Assignee field from the last created task. Today, I can rollup the last task (with MAX(values)), but can't pull any field beside the date field. How was this validated? ... Who is the target audience? Everyone who uses linked records. ... View more

The product could be a plugin or widget that allows users to create dynamic dropdown menus for single select questions in forms. Instead of a static list of options, the menu would display different options based on the user's previous selections or inputs. For example, let's say you were filling out a form to order a custom pizza. The first question might ask you to select a crust type (thin, thick, gluten-free, etc.). Once you select a crust type, the dropdown menu for the next question (e.g. sauce options) would dynamically update to display only the sauces that are available for the selected crust type. The same logic could be applied to a variety of form types, such as surveys, job applications, or product order forms. The product could be customizable to allow users to set up their own rules for dynamic option selection based on their specific form needs. Overall, this product could improve the user experience by making forms more interactive and efficient, while also reducing the likelihood of user error by only displaying relevant options. ... View more

Please add a field that functions similar to "Enhanced Rich Text" on Power Apps sharepoint or even better similar to a "Page" in Notion.  For example, ability to copy/paste screenshots/images, add tables within field etc. ... View more