If I’m understanding this correctly, you made a Dataview table that allows you to change the property of one of your task notes in a separate file from the file containing the Dataview table? If so, that’s super neat and I’m going to swipe that idea to use, myself.
I wanted to do something similar some time ago, but I didn’t want to depend on neither buttons nor meta bind plugins, so then I used an ordinary <input> with a script attached, which used the app.fileManager.processFrontMatter() to change the file(s) in question. This is illustrated in the post below:
Is this a better solution than yours, @Skallaturi ? Not really, but it’s an alternate approach which could be an option in some cases. What I really like about your solution is that it hides away all the logic to edit the other files. (Which kind of is also what I like about my variant)
It all depends on what you want, and how much coding you want to do. I just wanted to showcase that other variant alongside, for future prospects looking into stuff like this.
I wonder: Is it possible to use this in combination with pure dataview as well?
So if you create a folder in your vault, and insert the following code into it:
My test files: [[t94626-1]] [[t94626-2]] [[t94626-3]] [[t94626-4]]
## Files in folder
```dataview
TABLE field1, field2, field3, why
WHERE file != this.file and file.folder = this.file.folder
```
## With meta-bind
```dataview
TABLE
"`INPUT[inlineSelect(option(one), option(two), option(three), option(four)):"+file.path+"#field1]`" as field1select,
"`INPUT[toggle:"+file.path+"#field2]`" as field2toggle,
"`INPUT[datePicker:"+file.path+"#field3]`" as field2datePicker
WHERE file.folder = this.file.folder AND file != this.file
```