It's quite annoying when you need to need to add another variable to a script, but it only lets you append to the end. They are always presented in a consistent order, so it's a bit of an artificial limitation that one cannot change this presentation. Say I have these groupName groupNumber thingName thingTime ...and I want to add groupCoordinator, it becomes disorganised. Long input lists are worse because you may have related inputs that don't even show on the same page (it only fits ~4 at a time, for me). A button/link to sort by name would also be helpful. To work around it, I have to add an extra input slot, then edit existing variables from the bottom up to create an adjacent space. Tokens in values cannot be dragged & dropped, nor cut & pasted, which can introduce errors. It just doesn't make sense to have an ordered list where the order is immutable. ... View more

I have built a list view and would like to move around the records based on how we rank them in a meeting.  It would be great to move a record up/down without having the record nest within another record.  Am I missing a feature on how to do this?  A workaround would be to create a column for rank and sort them after they are ranked - not the easiest for mid-meeting workflow. See video here recorded with Vidyard. ... 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

The ability to set defaults at levels higher than field: base, workspace, team, user or account level for time zones and date, number and currency formats. For accounts or workspaces where all users consistently work in the same locale that is not the US, it would save base builders a lot of work in setup, double-checking and troubleshooting, and avoid many mistakes caused by inconsistencies and discrepancies for the whole organization.   ... View more

Currently, Calendar interface users can collapse weekends by switching a setting in the timescale: My suggestion is to have this setting available to creators, enabling them to change the default interface setting: As you can see, currently this is not possible. ... View more

When assigning a collaborator to a User field, it would be nice if we could direct users to a specific URL via the notification they receive. Currently clicking the email link or the notification sends users to the expanded record in the view where the collaborator assignment happened, but this is less useful in various cases. For example, in a table I'm creating, I have the access to assign a collaborator to the "Assignee" field from multiple grid views and interface pages, but I'd like for anyone that receives the notification to be directed to a different interface page where that can see their assigned records. ... View more

What is the proposed idea/solution? The ability to group sets of fields together for hiding/unhiding, moving around etc.  How does it solve the user problems? it makes it easier to determine and see which fields are applicable in which views. Making changes to views is easier to track in large bases with many fields where not all fields are applicable for every record.  How was this validated? Logic?  Who is the target audience? Everyone.  ... View more