What is the proposed idea/solution? The proposed solution is to enable interface creators in Airtable to add images to an interface during the design process. This feature would allow the inclusion of static imagery, such as logos, background images, instructional graphics, or decorative elements, directly into the layout of Airtable Interfaces. The aim is to enhance the aesthetic appeal and instructional clarity of these interfaces. How does it solve the user problems? This feature addresses the need for more visually engaging and informative interfaces. By allowing creators to add relevant images, it makes interfaces more intuitive and tailored to specific use cases. For instance, a logo can reinforce branding, instructional images can guide users through complex datasets, and decorative elements can improve the overall user experience, making data interaction more enjoyable and efficient. How is this validated? Validation for this feature can come from user feedback, requests, and the observed trends in interface design across other platforms. Users who seek to create more personalized and visually appealing interfaces often express the need for such capabilities. Additionally, benchmarking against other data management tools that offer advanced interface customisation options, including imagery, can further validate the need and effectiveness of this feature. ... View more

I think a key missing feature is the ability to embed items into an interface. I think this could take one of two (or both) forms. 1. A field that functions kind of like a "document" field. You insert an embed link. When viewed in a base, or in a grid/list view, it just shows as a preview - But when viewed in a record details pane - it translates to a custom sizable-embedded page. Each record's embedded view is based on the link in the field - just like the Button field type.  2. A "hard-coded" form - kind of like the difference between the "button field type" and the buttons you can set up in an interface. In the from-scratch interface builder - there would be a new element type called "Embed" where you could manual populate to with whatever embedded link needed. For example a google doc - or a news feed, etc. This by itself would accomplish half of the ideas that users have been putting forward for new automation triggers and integrations.    ... View more

Overview: We cannot create new Linked records when submitting a form. There is only the ability to create a new Linked record after the initial form is submitted (and record created). This is not conducive to some workflows, where it would be very helpful to create a linked record during the initial record creation process. Feature Request: Allow users to directly create linked records while they are in the process of submitting the initial Form/record in Interfaces. Current Workarounds: Provide a link on the initial Form for a user to open up another form to create the linked record prior to them completing the initial form. Create additional fields in the table and then use automations to automatically create linked records in the background when those are selected.   ... View more

To whom it may concern, An enhancement suggestion from Kalypso: In Interfaces, add more background color options and allow adding background color to single elements including list views, Grid, views, etc. that are not grouped with other elements. Alternatively or additionally, enable full background color capabilities that all elements sit on top of Expected Benefits: Improved aesthetics for Interfaces. Please consider adding this capability.  Regards, Jason Knighten ... 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

Hi everyone, Pello here from Moonland. As an Airtable Gold Partner, we’ve had the chance to build some pretty sophisticated tools in Airtable, like full ERPs and other complex systems. While we’ve been able to do a lot, there’s one feature that’s still missing that I think could help us build the perfect app: conditional pop-ups. What is the proposed idea/solution? The idea is to introduce a feature in Airtable that allows users to create and trigger conditional pop-ups when a button is clicked. These pop-ups could be customized to display warning messages, confirmation prompts, or any other relevant information before proceeding with an automation or action. How does it solve the user problems? This feature would enhance user experience by adding an extra layer of interactivity and control within Airtable. It helps prevent unintended actions by allowing users to confirm or review their choices before triggering potentially irreversible automations. This can be especially valuable in complex workflows where a simple mistake could lead to significant issues, such as data loss or incorrect processing. How was this validated? The need for this feature has been observed in various user scenarios where preventing accidental triggers is critical. Many users currently have to create complex workarounds or additional fields to mimic this functionality, which can lead to confusion and inefficiency. By implementing native pop-up functionality, Airtable can streamline these processes and reduce the need for such workarounds. Who is the target audience? This feature would benefit a wide range of Airtable users, particularly those managing complex workflows, such as project managers, product developers, and anyone using Airtable for tasks that involve critical or sensitive actions. It’s especially useful for industries like software development, inventory management, and any scenario where automated actions need to be carefully controlled.   I’d love to hear your thoughts on this idea. We’re always looking for ways to improve the tools we create, and your feedback could really help. Thanks for reading this post! Pello ... View more

What is the proposed idea/solution? Currently we've got the option of formatting a formula field as a single select, I'd like to format it as a muliple choice How does is solve the user problems? I'd use this feature for labeling records with what fields still need to be filled. Lets say the Name and Email fields are empty, it would show at the top of the record red labels of what information still needs to be filled in the record, and as you enter the info, the labels disappear. Yes you can use automations with a script for this, but it doesn't work instant. it takes 10-15 seconds per run. using a formula would be instant. ... View more

What is the proposed idea/solution? Allow the same "record detail page" to be used across multiple interfaces   How does is solve the user problems? Currently a designed "record detail page" is restricted to ONE interface. However, since we can incorporate multiple interfaces across one app (via the left nav bar navigation in interfaces), it is common to need to access the same record from a different interface. Currently you have to rebuild the the record detail page for every interface that it's data is used in. (We currently have 4 interfaces, so we have to duplicate 4 times). Not only that, every time we make a change we have to change it in 4 places. ALTERNATE SOLUTION The add the ability to group pages on the left nav panel without needing to stick them into different interfaces.    How was this validated? At my company we've probably wasted 200 hours trying to keep our record details pages in sync,   Who is the target audience? Interface app builders ... View more

First, let me start off by saying how incredibly important this feature is. The data so many organizations could have by being able to create custom calculated metrics in Interfaces is untellable. When creating big numbers (like the Numbers widget in an Interface), you are tired to a specific field, then you must select an operator. For example, you tie that Number widget to a field in one of your tables, for example, “Revenue,” then select “Sum” and it gives you the total. Let’s say you did that same thing for “Profit.” Then, with those two metrics, there is no way to create a third one based off those that calculates, for example, something like: Profit / Revenue (displayed as a percentage (Margin)). The problem is that the only workaround to achieve the above (something that is a basic feature in, for example, Google Data Studio), is to build in the Profit, Revenue, and Margin fields at the table level which can fail to work if you are dealing with a metric for which there is no workable operator. For example, you cannot use “Sum” in the settings of a Number widget in an Interface in order to sum up all the “Margin” values in your table. That doesn’t make sense. Long story short, I would love if, in Interfaces, you could calculate your own metrics. The flexibility this would provide would help people who are using Interfaces for basic financial or other number-based widgets, and could give them the insights they need (like the organization I work for!). ... View more