What is the proposed idea/solution? Give the user a way to switch the font used to render numeric data. This would allow me to switch to a font that has fixed width numerics so numbers have identical sizes. How does is solve the user problems? In pivot tables, make 100.000 and 111.111 look equally big. Currently the first will look like a huge number. The second will look tiny in comparison. How was this validated? Look at any table with numbers. See that 1 is not treated the same as 8 (width-wise) Who is the target audience? People who like to have a quick-look at a large quantity of numbers and not have to translate the things they see internally. ps. there is no label for User Interface. ... 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 created an interface that pulls from one table in my Base. With some of the demos I've seen on how interfaces can be used, I thought this would be a great way to display non-sensitive data via a public share link. Other tables in this base, however, do contain PII and cannot be shared with the public. So, after creating a lovely interface that seemed it would do exactly what was desired, I tried to share and found that I can only share with individuals who are signed in and have access to the base. Chat support let me know that the Base's permissions determine the interface's share permissions. In my specific use case, I have a base that shows all the volunteers that work with my organization, including a table for their basic contact info, a table for their engagements with us, a table for touchpoints we have with them, and another table that holds all the categories of expertise for our volunteers. The interface is based on this last table, and is a record review that tallies the number of available volunteers with each area of expertise. The data on that table is fine to share publicly, but not data from the others. Ideally, when building an interface you could choose how to share the individual interface without the whole base being set to public. Anyone with ideas of workarounds, I'm all ears! ... View more

What is the proposed idea/solution? When using a bar chart, when a date field is selected as the X-axis, there should be an option to not only list all the dates for a record, but to think of that axis as a timeline, where all dates are represented not just ones that exist in a record. How does is solve the user problems? I want to track usage of an asset over time. The Y axis is usage in hours, the X axis is a date, the records contain a field for date and a single time for hours. There are many days when the asset is not used. I would like those blank days to be reflected in X-axis; I do not want to work around that would have a record for every day, records only exist for days where there is usage. How was this validated? ... Who is the target audience? Users who have date fields whose records do not contain all of the dates in a given time period, who would like a true timeline view but for data that varies over time where a timeline chart is insufficient. ... View more

This would make everything a lot easier. What i have in mind is that when creating an automation based on an interface, you would be able to access all data displayed in the interface, not just the record the Automation is connected to. ... View more

What is the proposed idea/solution? I propose to add a way to organize tables by groups as MS Access does. Currently tables in a base are organized by tabs in a row on the top. I understand that this would be against the Excel-like feeling, where the workbook is organized in sheets, which are actually tabs. But I think MS Access way to organize the tables in groups is much better. This feature would get bases much more organized. For example I would create the following organization for my tables: 1) Entities groups. In each of these groups, I would put just the entities which I am dealing with to model my universe (for example, Student, Tuition for a school or Order, item for a procurement etc.) 2) Lookup Tables. All lookups that cannot be implemented with a single field dropdown list. For example a ROLE table which requires a field like Title, but also a description and maybe other fields like Hourly Rate etc. 3) Many-to-Many associations Tables. For all associations that need to be materialized, because you need to record information for each association. For example, when you assign a parking to a car. The association table is the place where to store the arrival date/time and departure. Table types 2 and 3 are quickly proliferating and pollute the data model led by the tables that deal with pure entities. How does is solve the user problems? I would suggest to implement it as a toggle to the interface, so that the users could switch between the two layouts as they wish. Excel-like (tabs in a row) or Access-like (groups of tabs in a side column).  How was this validated? MS Access actually adopts this way to organize multiple tables. Who is the target audience? Airtable users who works directly with tables and base designer. ... View more

I would like to propose an enhancement to Interface Builder regarding new record creation.   I created an automation that will auto-populate three fields in the Data View when a new record is created on my "Entries" table.  The automation works as expected in Data View, however, when I create a new "Entry" record in the Interface Builder, the fields that are set to auto-populate in Data View do not auto-populate in Interface Builder.   I know that creating the record in Interface Builder, closing the record and then opening that same record in Interface Builder will reveal that those fields have been auto-populated on the backend, however, the User Experience (UX) is (I think) greatly impacted by potentially causing confusion at best and unnecessary / time-consuming rework at worst. This enhancement would also send a positive signal to those who have invested signifiant amounts of time crafting their automation workflows.  Having a more consistent experience across the Airtable platform is a win for the platform and the users. ... View more

Option to Limit the Access to Interfaces. I want to build an App for my co-workers that are not that techie. So i want to keep them from seeing the Base and only allow them to see certain areas of an Interface. Would be helpful for customers too. Sadly there is no way, as far as i can see ... View more

I'm a HUGE fan of interface builder and it's becoming more of a replacement for my day-to-day interactions with my Airtable bases.  One feature that I would like to see added to the Button options is "Open Interface Form".  Below is a screenshot of the current list of options that I would like to see extended.   Because Interface forms offer a much tighter integration with Interface builder (not to mention increased usability and elevated design) it would be nice to have the option to create new records via Interface Builder forms without having to add a record picker and then selecting the option to create new item (as seen in image below) If this feature is already in the pipeline, thank you! If not, I hope to garner enough support from the community to get this feature on the roadmap.   Thanks for lending me your ear and I welcome any feedback / questions. Justin       ... View more