What is the proposed idea/solution? Option to colour table tabs in classic grid view. How does is solve the user problems? As a database grows, there can be quite a lot of tables in a base. Mine has 25 tables that I use. It gets tedious looking for the right table. If there was an option to colour table tabs by topic, it would be much more intuitive to find the right table quickly. How was this validated? From experience - I often find myself searching for a table, especially when I'm working on a laptop screen (13-15'') and not all the tables are displayed at once. Who is the target audience? Anyone with more than 10 tables in a base. ... View more

What is the proposed idea/solution? Formula fields have recently gained the ability to be formatted as single selects and checkboxes. I propose that formula fields also have the ability to be formatted as users and rich text. How does is solve the user problems? User fields are very useful for filtering records in interfaces, especially for filtering on the "current user". However, currently, the filter only works on actual user fields, but sometimes the user should be a calculated value. For example, a record might have a different assignee, depending on the stage of the record. It would be useful to have a formula field calculate the current assignee so that the interface page can then show all of the records where the user is a current assignee. For rich text fields, I currently have a formula field that serves as a template to build paragraphs in markdown, combined with an automation that copies the formula result to a rich text field. If the formula field could be formatted directly as rich text, I would not need the helper rich text field or the automation. This would also reduce issues with determining when the automation needs to be re-triggered.  How was this validated? Based on my experience with Airtable, I think these features would be useful. Who is the target audience? ... ... 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

What is the proposed idea/solution? This is a crosspost in the actual 'ideas' forum. I originally proposed this here When opening a record details page (sidesheet/full page), I'd like to be able to press a button to open the same record details but in a different, customized record detail page. I have so many customized record detail pages that I would love to make use of, but the only way to currently do that is in a different interface page, or use the 'open url in record' hack that has to reload the entire page to work, which is a bit clunky. How does is solve the user problems? Simple use case: open record details to view information that is not edit'able, click button to open the edit'able version of the record. How was this validated? I use hacks on every single one of my airtable apps to do this already. Who is the target audience? Honestly, I can imagine just about every interface-builder would use this. It would open so many options. ... View more

What is the proposed idea/solution? In the Timeline view, I'd love to see a slightly more granular hourly view than "Day split into hours." Most of the records in my base are no more than an hour long, and there tend to be a few phases of the day where they bunch up a lot, which makes the "Day split into hours" zoom level really difficult to read. If there were something more zoomed in, even something as simple as "12 hours split into hours," that would help a lot. (The ability to freely zoom would be even better, but that might be too much to hope for!) When it comes to looking at shorter-duration events at a glance, the calendar view is easier to read, but Grouping is where the Timeline shines, and exactly what I need it for. ... View more

It would be nice to be able to customize the content of tooltip in Interface charts by selecting another fields to be displayed in the tooltip. ... View more

What is the proposed idea/solution? Include the ability to "store" or "save" scripts and processes for reuse in multiple automations.  How does it solve the user problems? Instead of having to manage multiple automations using the same script/process, they can be modified/updated in a single place and update all automations that use them once changes are published. Pipedream does a nice job of this. It would save me a lot of time, and reduce the potential for errors. How was this validated? Personal experience managing complex automations Who is the target audience? Airtable power users and consultants ... View more

What is the proposed idea/solution? This idea proposes more dynamic options for scaling, rotating or providing 'hovering information' for text in Field Headings so they are readable when columns are narrow in Grid View and List Views. Currently text very easily becomes truncated and unreadable. Row height helps with field contents but not Field Headings. Hovering only works if there is a Description in the Field.  Note: this idea is essentially requesting behavior that you see in most spreadsheet programs.    Here is a typical Grid view... When you shrink the columns it looks like this which is too easily truncated and unreadable... Proposed Idea A: Enable hovering context information for all text whether there is a Description in the Field or not.  If there is a Field Description it would be displayed underneath the Field Name in the floating context window.  Proposed Idea B: Field Names can be rotated (similar to spreadsheets). Maybe 45 and 90 (as shown below) Field Names and all other text scales down to ~6 point before it begins truncating. Like the 'In Progress' text below   Overall make the margins in all fields super tight.  Field Row Height can be changed so the text wraps and stacks. (Not shown below but you get the idea) ... How does is solve the user problems? Keeps information readable when trying to conserve screen real-estate.  ... How was this validated? Not validated yet.  ... Who is the target audience? Creators who are trying to show as much information as possible on the screen while keeping information readable.  ... ... View more

What is the proposed idea/solution? I propose the introduction of a new field type named "Location." This field would be specifically designed to handle address inputs more efficiently and accurately in tables and more specifically form fields. The key feature of this field would be its integration with an address autocomplete service, like Google Places API, to assist users in entering correct and standardized addresses. How does is solve the user problems? Enhanced Data Accuracy: Autocomplete would reduce the likelihood of errors and inconsistencies in address data entry, ensuring higher data quality. Improved User Experience: Users would find it easier and faster to input addresses, enhancing the overall usability of forms and databases. Streamlined Data Collection: For applications like CRM, event management, and logistics, where address data is crucial, this feature would streamline data collection and processing. Global Address Coverage: Leveraging a service like Google Places would provide access to a comprehensive and updated global address database. How was this validated? In our specific scenario, we receive engineering service requests from customers and clients through our website. A critical component of efficiently processing these requests is obtaining accurate location addresses. Currently, we find that only about 50% of the addresses submitted are correct. This inefficiency hampers our workflow, as we frequently need to allocate additional time and resources to verify and complete partial or incorrect addresses. Common issues we encounter include misspelled street names, inaccurate street suffixes (such as St., Ln., Dr., Ave.), and missing or erroneous zip codes. Who is the target audience? This feature would be immensely beneficial to any user who relies on storing and utilizing location addresses within Airtable. Given the platform's extensive user base, it's reasonable to assume that this encompasses a significant number of individuals and organizations. ... ... View more