What is the proposed idea/solution? In any view, you can show or hide fields. As that list grows and more are added, the list gets longer and sometimes out of order based on when things get added. The proposed idea is to create custom sections inside your hide field or x hidden fields menu at the top so you can easily keep track of your fields. When you click on the fields menu at the top, the idea is to have a "create section" button and drag and drop all your fields into whatever sections you want to create. How does this solve the user problems? It helps users stay more organized when dealing with a lot of field types inside of one tab for more robust situations. How was this validated? Airtable has sections built in already, where you can create sections inside of the views and automations sections. The same ideology should apply to the fields.  Who is the target audience? Users who are doing more robust and complicated views that have many field types. ... View more

What is the problem this is addressing? When using forms, we use linked records to make selections - in our case - a certain product to be used when we build out a quote.  Unfortunately, the current setup on the forms is limiting the record name.  If a record name is extremely long, its getting cut-off and our estimators and sales are making incorrect selections because they don't know the full product name in the system. We can try to come up with abbreviations for many parts in the product name, but that can also lead to confusion and result in the wrong products being selected during the quoting process, producing an inaccurate quote. What is the proposed idea/solution? There are 3 options we can see that would address this issue. Let the record selection screen go wider based on the record names so they don't get cut off. Let the record selection screen wrap the record names, making the record deeper if needed to show the full name. Have the record selection in the live form actually match how it is displayed in the form builder -- to allow a more detailed view with the photo of the product as pictured. How does is solve the user problems? Any of these solutions/suggestions would allow for more details on a linked record to appear so that the correct record could be selected.  While I would hope to have option 3 as the solution with the visual representation being used to make sure we are selecting the correct records, Options 1 and 2 (I would assume) would be easier fixes that could be applied to address the problem. Who is the target audience? Our current audience, in our case, is internal usage for employees to select the correct records to compile quotes and work orders with the correct products.  Eventually, if something like option 3 was used, this could be used for order systems that are open to consumers and clients, allowing them to make a selection on what they see when words fail them, allowing a clear selection to the product and allowing for more error proof ordering. ... 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

What is the proposed idea/solution? Suggestion of a new view type, Map view, this view would allow me to upload an image file (a map), make records and place the records onto the map. This would be an X,Y, coordinate field within the record.   How does is solve the user problems? This would help me when documenting / auditing equipment installed at a customer site! I would now be able to assign a physical location to each record and visually present a map with icons representing each item placed onto the map. How was this validated? I don't know. Who is the target audience? At the moment I am thinking Wi-Fi engineers, but this could also be attractive to anybody trying to record physical location data. ... View more

I paid for the pro version specifically for this feature and the fact that it wastes my prospects time by saying “you will be redirected in a few seconds to xyz url” makes this feature almost redundant because I don’t want people dropping off before they’re tagged on the next page with my facebook/google tracking pixels so I will have to use another software like typeform or jotform just because of this… ... View more

A very useful feature to have would be the ability to “drill-down” another level when working with Look-Up fields. We use AirTable to manage our company E-mail accounts and Distribution Lists (Distribution Lists are email addresses that contain members and distribute messages to all who are assigned to it, i.e. info@company.com can go to John, Mary, and Paul). Here is the basic set-up between 3 tables: Table PEOPLE contains a list of all employees, and links to EMAIL which contains all email addresses (including distribution lists) Table EMAIL links to DIST LISTS DIST LISTS contains a lookup field to list the names of people on each distribution list. I am running into this problem: because a distribution list’s members can contain OTHER distribution lists, I cannot get a comprehensive list of all members wherever this happens (which is often). For example (using arbitrary email addresses)… say "info@company.com" has 2 members: john.doe@company.com and hr@company.com "hr@company.com" has 2 members: jane.doe@company.com and jim.doe@company.com. The lookup field will only give me “John Doe” as a name as it doesn’t drill-down another layer to lookup the names under hr@company.com. I managed to set-up a second level of “Sub-Members” with some linking (a bit too complicated to explain here), but it would be so helpful to have the ability to look-up a second layer. I know this sounds complicated - I did my best to try and explain in the most simple way I could! ... View more

What is the proposed idea/solution? I wish our fields could be grouped when working in views ex) all pricing fields could be hidden at once, or all visible, with one click instead of death scrolling all fields How does is solve the user problems? We have over 100 fields, many of which have a hierarchical relationship we don't have access to. It makes scrolling through all our fields complicated, and our employees get lost and feel confused. How was this validated? There is an unlimited amount of fields we can add, organizational tools would be very helpful Who is the target audience? Bases with a lot of fields, complex formulas, or multiple teams working within the same table ... View more

We have a lot of bases in our workspace it would be great if workspaces supported groups. So you could group your bases in the same workspace. ... View more

Field: Button | Action: Trigger Airtable Automation The ability to trigger an Airtable Automation that has a webhook trigger step. ... View more