There are some feature requests here that can be generalized by this feature: Allow typed lists fields. That is, fields that are a list of values of some type. For example, multiple checkboxes, multiple urls, etc. Currently just a few types accept multiple values: selects, attachments and links to other records. Why not make this more consistent: every type can be single or multiple, that is a restriction on cardinality orthogonal to the type itself. I understand this is a bit at odds with modelling one to many relationships between tables, but it’s very convenient for simple fields (you already recognized it by providing multiple attachments and selects) and avoid having to cascade delete or removing orphans after deletion. ... View more

I’ve posted on this before. But seen no activity on it. I need this, soon if possible, because every single base of mine relies on this functionality. I REALLY want a link-to-record within the same table to create another link column that auto-populates. Or a type that will. I just spent all day trying to fudge around it, but it requires either (a) manual linking with every record, (b) at least two new columns on this and a completely separate table to copy/paste/formula, that requires basically a temporary duplicate entry and again, lots of manual entry. And this doesn’t update with new records. I’d love a hierarchically-grouped view, but I could make do with just this one feature; I want a second column to be created when I self-link a table!! Does anyone have a self-updating workaround to this? Because for the life of me I can’t find one. And I don’t want to fiddle around with Zapier, either, because any solution I can think of with that requires a paid account. Edit: For now I’ve settled with putting each level of hierarchy on a new table, and I can sort of see them grouped in a hierarchical format. With this (Probably the intended) use case, allowing lookups/rollups to pull actual linked records of linked records, so you can click through, would basically solve my problem. ... View more

It would be great to be able to duplicate automations once they have been built. I have a use case where I’m moving records from one table to one of two identical tables depending on what filter they fit into. I built the first automation, only to realize I had to completely redo the exact same work for the second destination. ... View more

There’s a bug in the Mac version of the desktop app where if you are dragging a scrollbar (horizontal or vertical) and the cursor moves outside of the app window, the scrolling stops. Then, when the cursor hovers back over the app, the scrolling continues, even if the mouse button is not down. It’s a jarring experience. Here is how to recreate: Desktop app is open and in focus the entire time. It’s helpful to decrease the size of the window so it is not full width/height of the screen. Click and hold scrollbar to drag. While you’re dragging, move the cursor outside of the boundaries of the app window. Scrolling should stop. Release mouse button. Move cursor back into the boundaries of the app window. Scrolling will continue based on mouse y-coordinates. You have to click anywhere to stop the scrolling. Compare to other apps (e.g.: Chrome) to see how this behavior is broken. I’m not using Apple’s mouse so don’t have touch or horizontal scrolling built-in. So clicking and dragging is the only way to scroll, especially horizontally and because there’s no track behind the scroll bar. Would love it if this was fixed. I def use Airtable less because it’s so difficult to view large tables because of this issue. Happy to provide any more details if that’s helpful. Thanks! Dwight ... View more

Hi, It would be really nice if I could have a 3rd field shown at the intersection of these two others. For instance, the countertop in the powder room is called “Topus Concrete”. Instead of a number, I would like if that name could be displayed instead of the quantity. I know you can click on the numbers to see all the records that it’s referencing, but in terms of printing this out and having it handy, the name would be far more useful. ... View more

Summary When selecting “Link to another record” as a field type, Airtable should allow automatic linking to all records. UI Change The current slider that allows linking to single or multiple records, should be changed to a selection menu of the following: Link to single records only Link to multiple records Link to all records automatically Rationale This new option would allow scenarios where another field computes its value from the values of another table, easily. For example, a column that computes the percentage of a value of this record against the total of all records would be simple, as the moving or current sum is automatically computed on the column based on all the records without having to re-link all of them. ... View more

When adding a linked records table in page designer, please give the ability to “Horizontal Align” each of the columns separately. I would like the price columns to be right justified, description to be left justified, and everything else centered. ... View more

It would be great if we had the ability to use the record coloring feature to flag records that satisfy any number of criteria based on any number of existing table fields, and to allow multiple color “flags” per record. I would love to be able to see, at a glance, when a record satisfies multiple criteria, but not have to create a really complicated formula field to accomplish the same goal. ... View more

I know this topic has been brought up before but I haven’t seen any topics about it post-table syncing implementation. Would really like the ability to hide tables in bases - specifically tables I have syncing. For the most part, I’m syncing the table and then using some automations to find and match to existing records and then using lookups to pull in the information I need. The synced table really isn’t providing any value except for the specific fields I’m looking up. So, if there was an ability to hide these tables it would lessen the cluster of unnecessary tables in a base but still allow for specific information to be pulled in, matched, and synced. ... View more