The UI search bar currently requires an exact match for records to appear in search results, which can be limiting, especially when searching for specific details like the last few digits of a serial number or microchip number. The Base table’s search bar offers a more advanced matching feature, allowing users to find records based on partial entries. To improve usability and efficiency, I suggest updating the UI search bar to offer similar functionality as the Base table search. This would eliminate the need to rely on the 'Filter' option for partial searches and better support workflows that depend on quickly finding specific data. Your urgent attention to this matter is appreciated. ... View more

Context Within an automation we use a repeating group action to update a set of records. We may want to update each of these records differently depending on a condition. Currently, we need to define several automations to do that, which is a problem since there is a limit in the number of automations that can be created for a database. Suggested solution If we could add conditional actions within the repeating group it would give us the possibilty to create only one automation. Thank you for considering Pascal ... 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? 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

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 your idea? Create a new role for users with interface-only access called Designer or something. These users could edit interface pages, show/hide fields, and even edit fields as necessary. They wouldn't be able to access the database or automations, or even add pages, but could modify existing pages as necessary. What Problem would it Solve? Users would be able to change values of some fields that they otherwise wouldn't be able to: single select, multiple select, etc. which can be helpful for users who accidentally create a value in these fields which are mispelled or have the wrong color etc. Users would be able to make minor cosmetic changes and move fields around as necessary.  Less time would be taken from developers for making modest changes and fixing simple mistakes Who would benefit? I think this would give some users a sense of control over their apps, so they're not entirely locked to users with editor/creator access. Especially for more minor issues - like fixing incorrect single select fields - having to wait for a user who is a creator to fix those fields or update colors might be considered a minor annoyance for users. It would also appeal to users who consider themselves more designers than database engineers and give them an intro into airtable app development. It would also save time for base creators who may be managing multiple apps so they don't have to focus on more minor things that are easily fixable.   ... View more

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

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

I know we can alphabetize all the options in a Multi Select field, but the field itself will display all the entries in the order in which they were selected. That should be an optional toggle, to let it display as it does currently or also alphabetically.  When looking at many records at a time, and trying to compare values in a Multi Select field, it makes it very messy and difficult.  ... View more