Hi Airtable Community, I hope this message finds you well. I have a suggestion for enhancing the user experience when dealing with automation errors. Idea: More User-Friendly Way to Display Automation Errors Overview: Currently, when an automation fails, the error is logged in the automation’s history, which is helpful for administrators and developers. However, for end-users who trigger these automations by inserting data, the error feedback is not as immediate or intuitive. Suggestion: I propose implementing a feature where automation errors can be displayed directly to the user who triggered the automation. This could be in the form of a bubble or pop-up notification. The notification would briefly explain the error and potentially offer guidance on how to resolve it. This immediate feedback would greatly enhance the user experience and streamline the troubleshooting process. Benefits: Immediate Feedback: Users get instant notifications of issues, reducing confusion and preventing repeated errors. Improved User Experience: Users can understand and address errors without needing to dive into the automation logs. Efficiency: Reduces the time spent by administrators and support teams on troubleshooting and resolving issues. Example Scenario: Imagine a user enters data into a form that triggers an automation to update records in another table. If the automation encounters an error (e.g., due to a missing required field or a data type mismatch), the user would see a bubble notification like, "Error: Missing required field 'Email'. Please fill it out and try again." I believe this feature would make Airtable even more user-friendly and efficient for everyone. Thank you for considering this suggestion. I look forward to hearing your thoughts and feedback. Best regards, Nemanja Vukmirovic ... View more

What is the proposed idea/solution? Make Interface (Dashboard) information available in IOS Widgets. How does is solve the user problems? Users can have Data right at their fingertips, be confronted with the most important data at all times. How was this validated? We use Interfaces to bring together the most important business information. with widgets we could make this data even more accessible.  Who is the target audience? All Users ... View more

What is the proposed idea/solution? Allow visual representations for extensions such as Base Schéma, Org Charts or Maps to be included in the Interface pages.  How does is solve the user problems? ... How was this validated? ... Who is the target audience? ... ... View more

Hi, Not sure if my previous post worked, but one of the comments from the team at work is that the grid views are messy when it's a whole page of 'pill' shapes, particularly when they're all different widths (based on the text length of each option). Is there the ability to: 1. Shade/colour the entire cell instead of just a pill shape? 2. If not, can the width of the pills be based on the width of the column instead of the text length, so they're clear and a consistent width regardless of the dropdown option selected? 3. And, can white be included as a pill colour so we can have drop-down fields that look like plain text? These would significantly help with clarity when reading grid views. Cheers, Andrew   ... View more

What is the proposed idea/solution? Display a character counter over the limit assigned to a question in a form. How does it solve the user problems? Whoever is filling the form can know there is a character limit before they start typing their answer and this helps them manage their content better. Also, they will be able to adjust their answer without leaving the page to use a character counter in some other tool. (like Google Docs) How was this validated? An external contact called us for help resolving the error message they were receiving about exceeding the character count in a form we created, so we asked them to type their answers in a Google Docs file and guided them on how to access the character count there. They couldn't complete the form without the use of an external character counter. Who is the target audience? Anyone, whether internal or external, who will need to fill out a form designed and shared by Airtable users.  ... View more

It would be great if there was an option to allow for CSV imports within interfaces. 2 potential use cases are: The ability to upload CSV's in a list view that adds new records to the list The ability to upload CSV's in a Record Detail View that would automatically add child records to a list/linked record field I'm sure there are plenty more scenarios but these are the 2 I'm currently facing. ... 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

What is the proposed idea/solution? I suggest introducing a test/production environment feature in Airtable that applies to the data automations and interface sections of a base. This would allow users to create and test changes within a "test" version of a base, including data modifications and interface updates etc.. without impacting the live production environment. Once the changes have been fully tested and validated, users could publish these changes to the production environment, ensuring that the live base remains stable and unaffected during the testing phase. How does is solve the user problems? Comprehensive Risk Mitigation: It provides a safe environment for users to experiment with data, automations and interface changes, minimizing the risk of disrupting the live base. Increased Confidence in Updates: Users can test new workflows, interface layouts, formulas, scripts, and automations comprehensively in isolation, ensuring everything works correctly before pushing changes live. Streamlined Workflow: This would eliminate the need for cumbersome workarounds, such as duplicating bases for testing, and reduce confusion caused by multiple versions. It would also allow for seamless transitions from testing to production, improving overall efficiency. Who is the target audience? Power Users: Those who use Airtable for complex projects and need to test changes before going live. Teams and Organizations: Groups relying on Airtable for collaboration, requiring safe testing environments to avoid disruptions. Developers and Technical Users: Those building custom scripts or integrations who need a sandbox for experimentation. Project Managers: Responsible for maintaining base integrity, ensuring changes are vetted before deployment. Consultants: Professionals managing Airtable for clients, needing to demo changes safely before applying them to live bases Thank you Team Airtable ! ... View more

What is the proposed idea/solution? Disabling an action would skip that action during the automation run. How does is solve the user problems? This would allow me to build out actions, as they are supposed to be, but turn them off so I am only using the actions when I am ready for them.  How was this validated? I am currently building out a brand new system where multiple people get notified at different stages of the process. I need to build out the notification actions but I don't want those actions to run, to avoid annoying active users with system testing. Who is the target audience? Anybody that uses automations in Airtable. ... View more