Is it possible to list non-task bullets?

[crazymedguy]

For example in my daily notes, I have

name of file: [[2022-05-29]]

- [[PAID]] - [item::Membership] for [cost::123] [recurring::true]
- [[PAID]] - [item::apples] for [cost::11] [recurring::false]

Wondering if possible to list them like:

date	item	cost	recurring
2022-05-29	Membership	123	true
2022-05-29	apples	11	false

Thank you!

[MugenLee]

yes, this is a very useful function, and this scene will be involved in daily

Also I would like to know if this can be displayed using a list, which would be more intuitive than a table

like this:

[AB1908]

Is currently indexed in the beta version under file.lists

[blacksmithgu]

file.lists indexes all list elements in a note; it's easier to use from DataviewJS to render as a task view (like dv.taskList(dv.pages().file.lists).

[crazymedguy]

file.lists indexes all list elements in a note; it's easier to use from DataviewJS to render as a task view (like dv.taskList(dv.pages().file.lists).

How would I go about doing my OP question?

[blacksmithgu]

Something like this -

TABLE file.link, item.item AS "Item", item.cost AS "Cost", item.recurring AS "Recurring" FROM #source
FLATTEN file.lists AS item
WHERE contains(item.text, "[[PAID]]")

[crazymedguy]

Thank you!!

[DeutscheGabanna]

TABLE file.link, item.item AS "Item", item.cost AS "Cost", item.recurring AS "Recurring" FROM #source
FLATTEN file.lists AS item
WHERE contains(item.text, "[[PAID]]")

Could you please explain the logic behind stuff like item.item or item.cost? How does dataview connect two separate inline fields into one object if they're not nested? I'd sooner believe in something like this:

[item:: this is a [cost:: 59] USD toothbrush]
--> item.cost

than in this

[item:: this is a toothbrush] [cost:: 59] USD
--> item.cost

[DeutscheGabanna]

I know your stuff works because I tested it, but before I apply this in my own cases, I have to understand it :/

[DeutscheGabanna]

Also - how would an equivalent dataviewJS query look?

[blacksmithgu]

If you are referring to this query -

TABLE file.link, item.item AS "Item", item.cost AS "Cost", item.recurring AS "Recurring" FROM #source
FLATTEN file.lists AS item
WHERE contains(item.text, "[[PAID]]")

Then the magic is in FLATTEN. Queries are over pages by default - using flatten lets me "flatten" each page into a list of list items, where I now have one table row per entry in file.lists. The AS part names the data in each list item as "item", which I can then reference to get data inside of it like item.cost, item.item, and so on.

[blacksmithgu]

If you want to see this for yourself, try doing something like

TABLE item FROM #source
FLATTEN file.lists AS item

And see the output.