A core base can't do it, as of October 2026. The help page says the table shows a row for each file, so a list property stays in one cell. Dataview's FLATTEN command gives a row for each item outside Bases, and the Flatten Table plugin does it inside a base.
The request is small and specific. A forum topic from 2025-09-08 asks for a Dataview FLATTEN solution in Bases, and it has 10 likes and 3 posts.
The poster keeps a list of roles in each person note, with dates for every role. The goal is one table row for each role. In Bases, the post says, that would take a stub note for every role.
Split the list. Each item becomes its own small note, with the item's fields as properties and a link back to the parent note. The base then has one row for each item, because it has one row for each file.
Sort, group, filter and column summaries of the core table then work on those rows.
Dataview is a community plugin with its own query language. Its docs say FLATTEN takes an array in every row and yields one result row for each entry.
You write the query in a dataview code block in a note, and the table shows there. The docs example flattens an authors field to give one row for each author.
Flatten Table adds a view type named Flatten table. Pick a list property in the view options, and each item becomes one row with a Source column that links to its note.
When the items are objects, each key is a column. Click a column header to sort. Numbers sort as numbers, and dates in the form YYYY-MM-DD sort in date order.
MIT · no telemetry · core features free
Write a list of objects in the properties of your notes. Use source mode, because the Properties panel can't edit such a list.
Install Flatten Table from Community plugins and enable it. Check that the core plugin Bases is on.
Create a base, or open one. Set its filters so that it selects these notes, for example a folder or a tag.
Select the view menu in the base toolbar and add a view of the type Flatten table.
Open the view options. In List property, pick the property that holds the list.
When more than 50 notes have items, the table says how many it left out. Pro removes that limit.
No. The help page lists functions for lists, such as map, filter, flat and join. They change the list inside one cell. The table still shows one row for each file.
Not in core, as of October 2026. The help page puts nested properties under Not supported and recommends source mode. The community plugin Nested Properties says in its README that it shows nested objects and arrays as an editable tree in that panel.
Nothing, by default. A note where the property is missing or empty gives no row. Turn on Keep notes without items to get one empty row for such a note. A property that holds one value, not a list, gives one row.
Each item of a list property becomes its own table row in Bases, so one note can give many rows.
