Hi,
As I get better at using obsidian, the more fun this action-set brings!
Tonight I think I’ve caught a bug, when I use “Get Dataview List” with “LIST WITHOUT ID + an inline property” I get JSON string cannot be brought error.
Here is a video with the error:
https://youtu.be/CU0_mpfmJLA
Let me know if I can provide any additional information.
Cheers,
K
Hey. Interesting. Thanks for the report and the video, but could you provide an example of how you set/apply/use meditative_intention in your notes? I’ll try to reproduce the issue over here.
I mean, the JSON error shouldn’t pop up either way, but the more info I have, the higher the chance of finding the cause.
Thanks!
Sure!
I use inline meditative_intention to make a list of intentions from which I can choose what I want to work on today. These lines are located in daily journal notes.
Here is an example of one.
And here’s the workaround I use now.
Hope it helps 
Thanks for the addendum. I can replicate it, hooray! The issue only arises when more than one meditation entry is found in a single file. I noticed that in your video, there was a double bullet point, while in my simple test case there wasn’t. When I added a second medidation entry to one of the files, the JSON error popped up.
The reason is that the LIST result returned by Dataview returns a list, where each line in the list represents the results from a single file. When there is more than one entry for a file, the line contains a list of entries; when there is just one entry, it’s just one entry. Those lines are different in terms of structure, and AFO falls on its face.
The good news is that I found the root cause. The bad news is that, technically, it’s a Dataview thing…
I’ll see if I can build a workaround for that in Actions URI! I’ll keep you posted.
Nice!
For now I come up with a workaround with a replace text action:
At least for my case there is no noticeable difference to the “no id” query.
Provided the level of specificity of this bug, maybe you can just suggest this workaround in the action’s description.
Turns out the required workaround is a bit more involved, and it won’t be enough to change Actions URI. Meaning, the fix can only be rolled out as part of the next AFO update. Sorry.
I hope you don’t mind me suggesting it: Your regex it’s a bit loose for my taste (it’ll remove every wikilink followed by a colon), I’d personally change it to ^.+?: which removes everything from the beginning of each line up to and including the first colon.
Thanks for the suggestion!
