Grouping fields for Views

Savannah_Buswel · ‎Apr 21, 2023

What is the proposed idea/solution? I wish our fields could be grouped when working in views ex) all pricing fields could be hidden at once, or all visible, with one click instead of death scrolling all fields How does is solve the user problems? We have over 100 fields, many of which have a hierarchical relationship we don't have access to. It makes scrolling through all our fields complicated, and our employees get lost and feel confused. How was this validated? There is an unlimited amount of fields we can add, organizational tools would be very helpful Who is the target audience? Bases with a lot of fields, complex formulas, or multiple teams working within the same table

seanpmgallagher · ‎Mar 01, 2023

What is the proposed idea/solution? Create a single lookup field that a user can enter a company name or address and the autofill starts searching, similar to what is populated when you start typing an address into Google maps. Once selected, the company name, address 1, address 2, zip/postal, state/province and country are populated into the fields listed. How does is solve the user problems? This would provide address standardization and prevent users from having to search on google for an address and then enter that field either individually into each field or copy and paste the entire address. How was this validated? Not sure what this is asking Who is the target audience? Any company including addresses in their data fields. We include it in our CRM system for contacts and companies as well as in our project management bases for listing locations for projects.

Databaser · ‎Mar 01, 2023

Via the "hidden fields" button, we can select which fields are shown and reorder them. We can't however alphabetically sort this list. When you have a lot of fields, it would be useful to be able to do that. It would also be great, just like in some Interface functions I think, if the ones we select jump to the top of the list, so we don't have to manually drag them up.

dominicrannie · ‎Jan 31, 2023

What is the proposed idea/solution? It often makes sense to use a unique id field as the primary field in a database (for example "customer_id"), especially as linking records requires the primary field to be used. When this data is then displayed within an Interface, many of the interface elements will show the primary field in bold at the top of the record, when most end users would wish to see the customer name for example. How does is solve the user problems? Interfaces would be far more clear if records could be displayed with more control over if or how the primary field is displayed, allowing databases to reserve the primary field for unique data strings. How was this validated? ... Who is the target audience? Interface users.

Giorgio_Bazziga · ‎Jan 11, 2023

What is the proposed idea/solution? Airtable already allows barcode scanning in regular views, we need to make sure it works when a Form is being used How does is solve the user problems? It's intuitive for users that the feature would be available on the Form version. It also allows non-editors to have an easier way to enter data without needing a login How was this validated? Not sure I understand the questions Who is the target audience? Surveyors or anyone who wants field used

Karlstens · ‎Jan 07, 2023

Within an Automation Script, it's frustrating that we still encounter the inability to update the Single Select or Multi Select field options, with the error returning; "Airtable "Error: Cannot update field config from scripting automation" This limitation forces the user to reconsider the field type, with the alternative solution usually swapping it into a Single Line text field. Interestingly, it is possible to use an Automation Update Record action to do this exact same process, but for whatever reason it's not possible for an Automation Script to execute this very same process. Can this limitation please be reviewed and reconsidered by Airtable Developers? Without this feature, it limits the use of Single Select and Multiple Select fields within bases heavily dependent on Automations.

Sean_Murphy1 · ‎Dec 21, 2022

It seems that if I want to use a custom format for my Date field, I need to create a Formula field and use DATE_FORMAT(). Would it be preferable in most cases to offer a 'Custom' option in the 'Date format' menu in a Date field's settings? (see attachment) This would then show a text field where one could input the same formatting string one would give DATE_FORMAT(). That way I would not need to create a 'proxy' field to display the date as I prefer.

Arsalan_N · ‎Sep 18, 2019

It would be nice to copy over options from another Single Select field from another table

itoldusoandso · ‎Dec 31, 2021

This is a small styling suggestion to prettify the linked field pointing to a checkbox field in another table. The linked field has no styling option and all it shows is a tiny easy to overlook and boring grey check-mark. Could use some more style options similar to the actual checkbox field.

Roman_Scher · ‎Feb 12, 2019

Currently the sort order of a single select field is only useable when records in the same table are sorted by that field. Very often single selects are looked up in another table, causing the sort order to be lost and the records sorted alphabetically instead. To preserve the sort, the current alternatives are to 1. Create a formula field in the destination table that prepends numbers to each option in the lookup, which is not so pretty and error prone if options or names in the single select ever change, or 2. Break out the single select field into a new table with an additional ‘Sort Order’ field, which has to be filled in for each record, then looked up in the destination table – usually overkill. Since sorting order is already baked into single select fields, it would be awesome for this sorting behavior to carry over to any tables that look that field up! I can see how preserving the sorting behavior of the single select may cause confusion as a user if you’re unaware that the source field is a single select, but that may be alleviated if the lookup was also formatted with the same colors as the original single select, similar to how lookups of linked records are now formatted the same as linked records.

Grouping fields for Views

Autofill Address Lookup

sort field list alphabetically + selected ones on top

Allowing Interfaces to Use Non-Primary Fields as Header Text

Allow Barcode Scanning in the Forms

Allow createRecordsAsync() and updateRecordsAsync() to update Single and Multiple Select fields.

Custom date format in the Date field

Copy Dropdown menu options from another table

Add styling option to a linked checkbox field

Preserve the sort order of single select fields in lookups

Format Formula as Checkbox

CSV Import in Interfaces

React to Record Comments

Allow Emoji reactions to comments

Multiplying by percent column yields result that i...