My use case is being able to filter by a checkbox where I sometimes want to see both checked and unchecked records and other times just one or the other. If I had an “or”, I could have two filters for the checkbox and check one filter and not the other so all would display. ... View more

I am trying to manage somewhat small scale inventory/supply management. I need to receive supplies that have details attached, consume some supply to a process (linking some of the details) and also calculate the reduction in supply from on-hand stock. In order to do this I am finding I need at minimum 2 tables. I have been able to get everything to work except scanning the consumed item to process. The consumable is the linked field and is the barcode (primary field on source table). The only way to add the record, however, is with text. The same function in the search field would be very helpful for the entry ui of the linked records (little camera icon opens the camera and acts as the input device) ... View more

I would like to request the use of additional barcode scanners, other than the one on our phones. I work in a school and this would be immensely helpful in integrating student ID barcodes into many things we are building in airtable right now. P.S. Airtable has been a game changer for us. Thank you! ... View more

AirTable could benefit from making junction tables more of a feature than a workaround for bases requiring for many-to-many relationships. I’ll be using this mockup base (https://airtable.com/shrkWoMwtNLYAVvoH) as an example to explain these requested features. It has 3 tables: Projects , Firms , and Project Roles (the junction table). Each project will have a prime consultant, and may or may not have sub-consultants performing any of 20 or so roles (i.e. landscape architect, economist, contractor, cost estimator, etc.). 1. Junction record name “smart display” based on active table This example base follows a common junction table entry naming convention: the primary field is a Formula that concatenates the records to which it is linked (i.e. {Project Name}: {Role Type}: {Firm Name}) When I’m viewing the Projects table, it would be most useful if entries in the Team column (which links to the Project Roles junction) displayed like “{Role Type}: {Firm Name}”. But in the Firms table, it would be most useful if entries in the Project Roles column (which is the corresponding link to the Project Roles junction) displayed like “{Role Type}: {Project Name}” In other words, AirTable should understand which portion of the formulated entry name is implied by context (what is the active table) and hide/omit it to avoid redundancy. Alternatively there could be a new UI in the Customize Field Options that allows users to write a new formula/logic for a linked record’s display name for that column in that particular table to avoid repetitive info being displayed. 2. “Smart” linked record expand Since the junction table has to act as a middle man, I can’t just click on the linked team member from the Projects table to view their contact info, I’m instead taken to the Project Roles entry and from there I have to click on the linked Firm record to view more of their details. One could, in theory, add a Lookup Field for absolutely every column of every table to which the junction is joined, but the issue with such a workaround is obviously tedious and inopportune. 3. Assume “Add New Record” when clicking the “+” icon for a Linked Record Field pointing to a junction table Like many junction tables made in Airtable, the entries in the Project Roles junction table will only ever be linked to one Project and one Firm each. It is more intuitive for a person to make new entries in this case within the Projects table as the junction entry will automatically be linked to at least one of its major components. It would be ideal if the “+” icon to Add a Linked Record skipped the “select from existing records” dialogue and went straight to the “add new record” dialogue when linking to a junction table. 4. Hide a table Ideally, I will never have to even look at the Project Roles junction table once its set up. I’ll be adding all the new relationships from what is ostensibly the “main table”, in this case Projects . If I could have the option to hide the Project Roles table out of sight to avoid confusion, that’d be great. ... View more

Problem Users don’t get useful results when they group by multi-selects, array based, or comma separated values. In the example below, three recipes that include “Apples” end up in different groups. Whereas a new user might have wished all of the records were listed under “Apples” and then re-listed under other fruits as well. Solution Attempt Honestly, there might not be a good solution without breaking core Airtable functionality and database best practices. In other words, by introducing (gasp) duplicate records as described above. I’m imagining a toggle under the grouping menu where a setting section named something like “split lists & display duplicate records” could display extra records (with an option to set a deliminator). Might also be nice to have a visual indication within the grid when a record is a duplicate. So the above list would instead look like: Apples: Apples & Caramel Fruit Salad * Fruit Smoothie * Pears: Fruit Salad * Bananas: Fruit Smoothie * Known Workarounds A user could just filter a view by a group category (such as Apple), but this becomes cumbersome at scale. Or someone could write a script and print customized values to a table, but this isn’t ideal if you were grouping in order to more easily edit live data. ... View more

I commonly have fields with 15 or so options. I usually design the options elsewhere and then put them here. My issue is that I am not able to paste multiple options at the same time. Even if I select multiple cells, either in Airtable or a spreadsheet application, and paste into the options box, it puts all the cell contents in one option instead of creating multiple options. To give a concrete example, consider the following table. Options Description High High chance of conversion Medium Medium chance of conversion Low Low chance of conversion I select the three options in the first column and paste into the options part of a field’s configuration screen. My problem is that I get something like this: High Medium Low as one option, rather than three options. Could you please have this become three options? ... View more

Hello, We want to be able to search within attachments (word/ppt/pdf), similarly to typing a keyword in dropbox or google drive and getting results based on the presence of that word or phrase. PDF to text conversion is not a great solution for us since we have upwards of 3000 records and each record contains 2 attachments on average. Has anyone found a working solution? ... View more

When I try to have important information from another table shown in my current table, I use the lookup field. But what I don’t like is that the lookup is transformed into a simple text representation. So when I lookup a “single select” field that has rounded borders and colors, as a lookup, it’s only text with no color and no round borders. When I lookup a priority field with a star representation it’s even worse. It gets transformed into a number. So instead of having 4 stars, I get the number 4. Which is harder to read. All lookup fields lose their color and visual representation, which makes the table look dull and hard to read. I’d like to request the feature that lookup fields look exactly like in the table looked up from. If it’s pink hearts, it should be pink hearts. If it’s colored single select fields it should look like it. Information would be much easier to read and look at this way. Cheers Chris ... View more

Feature requests: Batch copy configuration from another view. From this Reddit thread. Automatically sync configuration from a view (such as the “main” view, whose default name is Grid view) with any other views for that table. ... View more