FEATURE REQUEST : inline fields, multiple assignments to the same field, added value

[sergeict]

SEE ALSO : [BUG] issue 107

Inline fields seems to be on a divergent road from "official" properties. They are an added value to DataCore and Dataview.

The question is "how to make them evolve ?"

Personally, I would opt to mainly keep the dataview way to operate since it provides while providing a few enhancements, in order to provide

• backward compatibility
• more flexibility to use fields ( i.e. incermental addition of values / multivalues at different places )
• smoother integration in fluid text.

I also note that a number of users currently benefit from the dataview feature of placing several inline fields with the same key in the same note or task. There are a number of use cases for this.

Currently, properties are attached to a note, as their parent context. DataCore adds more contexts than any other plugin : sections, blocks, lists and tasks. The parent context hence becomes more granular than ever while properties always belong to the page context.

I propose to put some effort on the inline fields per se as a valuable complement to the properties.

FEATURE REQUESTS :

1. do not drop the inline field feature, but enhance it - statement of direction -
2. allow incremental/multiple values by recursively assigning the same fiels, i.e. [field1:: value1] and further in the context [field1:: value2] should provide "value1, value2" as an answer to = this.field1 instead of the current DataCore answer "value2".
3. add controls for the above behaviours, namely (dis)allow inline fields and handle multiple assignments as multi-value or last value.

Many thanks for your valuable plugins.

[ces3001]

I use multiple occurances of the same inline key in notes, and love the accumulation of that key as an array in dataview. It would be amazing to query the inline field elements to get the section it was in, and then, somehow—miraculously—the date tag associated with that section. e.g.:

## subsection1
#date/2025/10/20
key:: value20

## subsection2
#date/2025/10/19
key:: value19

A lot to ask, but since we are on the topic.... why not?