Amazing Airtable team, please give us folders to organize those Automations. I have about 50 and have to plow through them. Ideally I would like to organize the automatons into folders and (in my case) I would name the folder similarly as the tables names where the automations are being used. That would make it easier to find the right automation I am looking for. ... View more

I’d like to create a Layout in Page designer and use that same layout for multiple tables inside the same Base. Is this possible? Thanks, Jake ... View more

I can get a list of field names by downloading the CSV and look at the header line. But is there a way to get a list of field definitions (field type, formula details?) ... View more

This subject may have been discussed in the past but I haven’t seen any solution. Now, I desperately want to share a dashboard (blocks) with a crowd of contractors, or at least single blocks which I may group as a dashboard on our website by embedded code. BUT: as long as the people I share the blocks with have full access to all tables I cannot do it. It must be possible to have the option to share a block where the “settings”, “show data”, etc. is simply to be enabled/disabled to protect the database. At the moment the share option for blocks seems totally contrary to the shared view option, where you can limit access to the data you really want to share. And limited access makes sense for blocks, too, doesn’t it? Help, help, as this issue is soooo essential in our projects where data is shared with thousands of people. Thanks & best regards, Kai ... View more

Please make the Expanded Record match the View in use. I use Airtable as a Project Management tool and we use the Expanded Record heavily. Its clunky right now with all the extra fields in there that don’t need to be seen. For us it really keeps us from being able to use Airtable to its full potential. I need to be able to get new people up and running quickly. Currently I have to explain which fields to ignore, etc. It’s just not clean and easy like the rest of your program. I’m trying to think like you here and I figure the least amount of work for Airtable team would be to simply match the Expanded Record with whatever the current View shows. This would solve my issue and for many others who have raised this. It would be continuing your great vision of having Views, which is really the most outstanding feature in Airtable. In an even better world you would have functionality to edit the Expanded Record in any way the user sees fit. But that can get complicated and might even take away from your vision of what Airtable does. So maybe later… ... View more

Please help to get Airtable Bases linking to each other, thanks! ... View more

I’m so desperate to have multiple URL entries in a single field. It’s so difficult to include URL references on a record when it requires more than one URL, and I have been frustrated with this for over a year to the extent that I just give up on using Airtable for many projects. Junction tables, which I have tried, are really not a good solution to this because: I don’t use most references more than once, so there’s no reason for me to have a separate record for some random URL. Having to create a record for every URL makes data entry that much more cumbersome (the reason I stop using Airtable), and The ability to click the URL in a URL field is too important. When the URL has to be its own record it just starts feeling clunky and frustrating. Furthermore, it’s implausible for me to just have multiple URL fields because while I often just use one or two references, sometimes I may need ten. Having to habitually scroll past a bunch of empty fields ends up making data entry sloppy in the longterm, because one gets used to mentally filtering out empty fields and then forgets to enter stuff when it matters. Aside from references, I can imagine this would be frustrating for contacts-type databases where a person or business may have multiple URLs associated with them. I have also found it frustrating when trying to compile research on a topic: things that ought to function as a tidy single record suddenly need to be their own table, or multiple tables, and it just gets silly and impractical. I would just really appreciate it if the URL field could just have multiple entries. It would make a huge difference and I would use Airtable a lot more, with a lot less frustration. ... View more

I have a table where the linked fields are references to other rows in the same table. I want to create a roll up field, but this isn’t allowed because the links aren’t to another table. Would it be possible to remove this restriction? ... View more

Continuing the discussion from Calendar View based on Lookup field dates: Now that Lookup fields work for Calendar Views, please extend this functionality to Kanban View. My use case… I have a base that covers our video content management and review process. Three key tables and fields are: Table of Videos: Title, Description, etc. Table of Reviews, including fields for when the last review was, a formula for when the next review is due, and who will do the review. Table of Account users, including fields for people’s name, their role in video content management, email address, and a Collaborator field type named Airtable user. (Most, but not all of the team will have Airtable accounts.) I’d like Kanban Views of Videos / Reviews stacked by the Lookup field which references a single Airtable user. Videos / Reviews kanbans would be stacked by each Airtable user assigned. Any Videos / Reviews assigned to team members who aren’t Airtable users would be listed in the Uncategorized stack. Lookup field extension is a massive feature extension for Calendar Views. Let’s do likewise for Kanban! :grinning_face_with_smiling_eyes: ... View more