New: List View

Hi ! This is awesome! 

One call out we are wondering about is are we not able to share list views through embed code or a shared link? I see this as a missed opportunity since we can do that with the other views. We heavily use the shared links.

Thank you!

Is there a roadmap for bringing the List View to the mobile device app? I'm really, really wanting to finally replace OneNote lists on mobile devices, and Airtable has the potential to achieve this, thanks to the new List View.

Pretty cool and useful for something we're building (we've replicated a checklist using a table.) Can't seem to get it working with interfaces though when data is selected from a list view. Says it cannot be used in this context. So would love to have that be supported in the future!

Also, was hoping that the Parent/Child tables could be linked via a Lookup Field, but at this stage only Link Fields are supported. Could we please have Lookup Fields also supported?

@Ayesha_Bose It would be way more preferable if all linked record fields allowed hierarchies (regardless of the view), instead of requiring an entirely separate view to gain this functionality. If you look at 3rd-party apps like On2Air Forms or MiniExtensions, they give the flexibility to have hierarchies anywhere on the screen & anywhere you have a linked record field.

@Ayesha_Bose Thank you for building this!! I often avoided Grid View interfaces because they felt too clunky. List view fixes this! 😃

I'm not able to do one thing with list view though.

I want the buttons I set up in my database record to be clickable in a view-only List interface. Currently, they look like buttons in the List interface, but you can't actually click on them.

This looks interesting, thanks! Off the bat I'm wondering if there's plans to add record colours? Also, would really appreciate some more advance warning of new features like this. I don't know what this would look like, maybe an opt-in mailing list? As the admin for a few users, I'd feel a lot more comfortable having a slight heads-up that everyone will suddenly get access to something I've not even seen yet.

Another couple of comments:

- On "Tall" and "Extra Tall" row heights, the first field of a level 1 record is aligned to the centre, vertically, whilst the subsequent records are aligned to the top/start

- The "Level 1", "Level 2", "Level 3" labelling feels backwards to me (aware this is just preference but Level 1 feels like it should be the top level). 

- List view makes the inability to add custom record labels even more glaring in its absence. First use case has 2 out of the three labels I need, which means I can't really use any

- The first two use cases I tried, really require 4 levels. Is this limitation expected to be temporary?

- This is kind of an old one but the list view is just another example of why it's needed; not being able to create linked records in an interface immediately disqualifies me from using the list view in the first two use cases I thought of

Hope this is received as it's intended, this could be a great addition to the toolset but just needs a little tweaking I think

I like the direction this is going, but for most of my setups it feels backwards since I work within the parent table to view children, so if I want to view a project's tasks I look from where the projects are listed. Unfortunately I'd need to push users to view from the lowest level - the task list - which would mean reshare and rebuild some things which isn't worth the effort. I could technically move tasks into the same table as projects and label them differently, but then I'd lose the benefit of multi-table hierarchy.

I love the idea in theory, but in practice it's hard to justify using it for anything existing since it feels backwards. This might just be my specific use case though.

Its looks great!! very useful to make a to do list across many proyects

Taking another look at the List View this morning, another limitation is that a self linking table, where a Link Field references the table it's created in, can't utilise that linked field in a Level 2 relationship - however, it can use that self-Linked field as a Nested Field, which could be useful.

So here we have a table with a field that represents a "Child" relationship.

Below is the List View that may be generated from this arrangement.

But you can't set the same stacked view if your table is geared with a parent relationship.

If your table has a Parent relationship, then you'll be limited to the below List. It looks back-to-front in my mind.

And due to the limitation of a Stacked View not being able to use a Linked Field that references its own table, there's not much you can do. This Parent based Table can't be reconfigured within the List View to look as per the first example, meaning a Table (... and maybe a Base) redesign would be needed to leverage the new List view.

I haven't exactly thought too deeply on why such limitations would exist - and perhaps there are reasons. Keen to hear others thoughts on this.

Great new view!

It would be great if we could collapse all levels at once or per level, like we can with grouping in gridd views. 

Also, when using a link to a sync view in a level, it doesn't show that record in the list view. I can understand that you couldn't change any data (of course), but showing the data should be possible imo. 

There's a bug - when I added the List view in my interface, and then shared only the interface (and not the base) with someone with an editor access, the person cannot view the pages in the interface where the list view is shown. The rest of the interface loads fine.

As shown in this image above, he keeps getting this error code: pglDPq0IuyIZbNXYz. However, when I gave him access to the base as well, the Interface loads fine without any errors. I've reproduced this error multiple times, and have received the same error every time.

Good afternoon @Ayesha_Bose,

Working with a client and their extensive base - whilst assessing the new List View, this is one problem that we encountered straight-away during the List views creation - the inability to copy another existing views visible fields.

Can a toggle please be added so that we can easily copy another views field visibility for each table/level?

@Kiersten_Kollin: Thanks for flagging this! Right now, we don't currently support the ability to share List views through a shared link. We do support List view in Interfaces and you can share a link to that with your team. We'll keep track of this feedback as well.

@Karlstens : Thanks for all the comments and apologies for the delay in getting back to you!

• We're very excited about mobile support here and have this on our roadmap. We don't yet have a specific estimated timeframe, but we're working on it!
• For Lookup fields, can you tell me more about why you need this instead of the linked record? Since you already have the linked record field in that table, you can show any fields from either of the tables in List view. If you have a specific example here, that would be super helpful.
• Thanks for flagging this. We currently only support linked records within the same table as nested records underneath the lowest level of your List view. With handling up to three tables, with an additional four level with nested records, we had to put in some limitations to handle complex cases (like when there are multiple parents, etc). We'll think more about this, but you may need to adjust some of your table schema to get the List view you need.
• That's a great suggestion, I'll pass this on to our team! I can see how copying those settings from another view would be really helpful and make this set-up much faster.

Please keep the comments coming, we really appreciate the feedback and it's super helpful for prioritization on our end.

@Rui_Chen1: Hmm that's unexpected! Do you have a screenshot of what you're experiencing? Would love to track this down if there's a bug here. 

@Jack_Manuel: Thanks for the feedback! We are actively working on this view, so this is really helpful for our team.

• Yes, we're working on supporting record colors very soon. I'll pass your feedback about an opt-in mailing list to our team.
•  On the row height alignment, that's intentional by design, but curious if it feels off to you.
• We went back and forth on this a lot, and ended up with our current numbering to resemble how it feels in a building going up floors. But this is definitely on our radar!
•  Right now, we don't have any plans to support custom record labels, but if there are specific ones you're looking for, we'd love to get them in and you can submit them via this form.
• We don't have any immediate plans to increase the number of levels, but would love to hear more about your use cases for more! You can get a 4th level by linking to records in the same table on your lowest level and enabling the ability to show nested records.
• We're working on this one, totally agree that this is important!

@Nick_Berg: Got it, that's super helpful feedback! Have you tried out List View in Interfaces? The technical limitation that we have within the Data tab where you have to start at the lowest level isn't there in Interfaces, so it might be a bit easier to build what you're looking for there.

@Databaser: Thanks for flagging these issues!

• You can expand/collapse an entire level if you right-click. It's pretty hidden right now, but hopefully that helps you.
• I'll follow up with the team on the synced data issue. 

@Adnan_Ahmed: Yikes, that's unexpected! I'll follow up with our team on this, thanks for flagging. 

@Ayesha_Bose 

There are a few bugs with List Views:

1. List Views don't work on Safari: 
https://www.loom.com/share/8f0213ea48884d5881c444e682e8d9d2

2. Manually sorting doesn't work:
https://www.loom.com/share/2246856bc362453c9c83c8460dc4aa14

Also, this is not a bug, but when I first read about this new feature, I was under the mistaken impression that list views would give people hierarchical filtering capabilities for data entry (e.g. choose a "Country", and then you are only prompted with a list of "States" that match that Country. Then, choose a "State", and then you are only prompted with a list of "Cities" that match that State). But after playing with the new list view, I see that it's just a new visual way of seeing linked records in Airtable. So it doesn't offer any new functionality per se — it's just a new cosmetic layer. Would be nice to have this hierarchical filtering functionality added to linked record fields, which is what you get in On2Air Forms & MiniExtensions.

@ScottWorld: Thanks for flagging these issues — the Looms are super helpful here! Please keep them coming as you run into anything.

• That Safari bug is weird, will flag to our team!
• Right now, we don't have any plans to support custom record labels, but if there are specific ones you're looking for, we'd love to get them in and you can submit them via this form.
• On manual re-ordering, this is on our radar. Right now, you can only drag and drop records across different parents, we don't support re-ordering within the same parent.
• There are a few new pieces of functionality in List view like allowing you to edit fields from multiple tables in one view, prefixing a checkbox field, show/hide sections with no children records, etc. Thanks for flagging those other tools, will take a look.

Just want to leave a "+1" here for the ability to share a list view (eg read only). 

@Ayesha_Bose 

• Row height alignment does feel off to me, although I can't give a good reason for this, just preference
• Again, level numbering is just a preference I think
• I know you offer the option to request labels but it's really off-putting, I just don't want to engage with the feature until I know for certain I can use the labels that work for my data
• The first use case I tried was for quotes, we have a project, which has attached quotes, which are comprised of sections, which are comprised of line items. 4-levels. I created a list view that incorporated quotes, sections and line items but the inability to group by project makes it unusable
• Off topic but the lack of a replies feature on the forum is making this thread quite annoying to follow