What is the proposed idea/solution? FieldArray() - A function to use within the Formula Field that allows for the concatenation of all fields values, with each entry separated by a comma. ReplaceLast() - A method that replaces the last matched character in a string, so for example, the last comma can be replaced with a more desirable string. How does is solve the user problems? It's incredible just how overly complex a formula needs to be to cater for what is simply concatenated field values that need to be separated by a comma. Take these fields for example; "Colour A" "Colour B" "Colour C" And the first record has red, green and blue. Using FieldArray(), we could do this within a formula; FieldArray({Colour A},{Colour B},{Colour C}) Which would return: "red, green, blue" Then, for example, we could do this; ReplaceLast( FieldArray({Colour A},{Colour B},{Colour C}), ", ", " and ") The result being; "red, green and blue" Or perhaps; ReplaceLast( FieldArray({Colour A},{Colour B},{Colour C}), ", ", " or ") "red, green or blue" Who is the target audience? Anyone who's tried to concatenate many fields together thinking it would be a two second job, only to find themselves entering some kind of nested formula hell.   ... View more

It would be great if we could get the barcode scanner working in forms. ... View more

While on the homepage, all the bases are crammed into a list or a grid in an untidy manner. Please introduce a higher hierarchy to introduce teams. Teams are creating their own set of bases which can be seen in one expansion, rather than scrolling through the entire page to see your specific base. ... View more

Airtable interfaces have totally changed the way we are able to work with our data. Working in the actual bases is becoming more and more an admisitrative task, designing and creating the data architecture as well as all processes working in the background (scripts, automations, extensions). A new type of interface experience This calls for a completely new powerful approach to how interfaces are organised and accessed. We would like end users to sign into their Airtable account and see something like a landing page of our company (workspace). There they are shown the interfaces they can access (permissions). Interfaces from all bases in that workspace. This landing page should have design features, so I can create this experience. A new type of user level? This also could call for a completely new category of users. People who exclusively work with data through interfaces and no longer have any contact with the base in the background. This user level could be divided into two groups: People being able to work with data: create new records, edit data, etc. People only viewing data New pricing modell? With this a whole new pricing modell could be considered. This modell would differentiate between admins, programmers, base editors and end users of which there would probably be more than the former. ... View more

What is the proposed idea/solution? Add passcode lock feature/option for iOS App How does is solve the user problems? Airtable stores a vast amount of data which may at time be confidential or require additional security.  Viewing of that data by persons other than intended could have detrimental consequencee. How was this validated? There is no lock feature in the app. Who is the target audience? Anyone who uses the mobile app. ... View more

Hi Team!  We're using page designer to export some of our form responses. It would be a great help if we could select multiple or highlight multiple data and move them at once, instead of moving them 1 by 1. Please let us know if this is possible. Thank you! ... View more

What is the proposed idea/solution? Labels for Fields within the Grid View. Form Views have them, but we need them in Grid Views too. How does is solve the user problems? Similarly to a Form View, I'd like to see Field Labels available for use within the Grid View. Labels become overly useful when tables are busy with countless fields that result in having complicated names usually to cater for schema and base design. But such complex Field Names become disconnected from their audience - such as when a Grid View is created, specific fields are shown (with their complicated base-design related field names) and then that view is shared/embedded with the read-only audience. The audience is left to consume the shared data with those awkwardly complex field names. One workaround is for the base designer to post-adjust those complex field names to something more simpler for their target audience - but this only works when the data is being consumed via one Grid View. If the field is to displayed (yet represent different data, thanks to clever/efficient base design), then the name must be left ambiguous to cater for the multiple views where that field is visible. Another workaround is to spin up many formula fields with the desired field name that simply reference the other complex fields, but this strikes me as bad design and I can't justify employing such an ugly workaround. To help explain this dilemma further - take my current hobby project for my local running club where I have a field called "Fastest Runner". Due to all the events, time fields, position fields, roll-ups and lookups, field name needs to be detailed for base design - such as "Fastest Runner (from Event) (excluding volunteers)" - or something similar. From there, this field is used in many Grid Views, four of which are exposed on the clubs website via Embedded Views - which is where the problem is. Four embedded Grid Views 10km - Mens Results 10km - Womens Results 5km - Mens Results 5km - Womens Results All of these Grid Views display Fastest Runner (from Event) (excluding volunteers) , but really, each one of them needs to have this name adjusted for the audience. Perhaps I'd like each view to have the field labelled as; Fasted Male Athlete Fasted Female Athlete Or maybe, Fasted Male 10km Athlete Fasted Female 10km Athlete Fasted Male 5km Athlete Fasted Female 5km Athlete And interestingly, this functionality actually exists (!) but only within the Form View - unfortunately not in the Grid View. Can we please have Field Labels available for use in the Grid View, where they'll be visible within an embedded view as the fields name? ... View more

What is the proposed idea/solution? An enhancement to the record selector that pops up in an Interface when you click on a Field element for a linked record. Currently it allows you to filter and select one option. I would like the ability to filter and select multiple options, eg by holding down the shift key. How does is solve the user problems? Linked Record fields can be linked to multiple records, however there is no straightforward way to assign multiple records in one shot. The filter allows you to see records that are related by a common part of their name -- it is too bad you have to repeatedly type in the common part of it because you can only select one record at a time.   ... View more

What is the proposed idea/solution? Allow individual rows to expand to fit long text (like "wrap text" in Google Sheets) or at least to fit MORE long text. How does is solve the user problems? Sometimes I want to skim my data (in my case customer emails), but I can't do so when I have to click into each individual record when long text fields get cut off (even when height is set to "Extra Tall"). Clicking into each record is a big time suck. Who is the target audience? Any Airtable user with long text fields, but specifically bases with customer emails. ... View more