Is it ever necessary to force Data-View to refresh it’s cache? If so... How?

[TheAtomAnt]

Just a quick note: I have tried "Drop all Cached File Metadata" and "Force Refresh All views and Blocks" they did not solve this issue.

Hey everyone, just looking for some suggestions on what to try next.
I created a dataviewjs view that queries a number of pages from my vault, and for each, renders a single line in a single column. As part of that line I render an html "button" and attach a click event handler to it. When I click on that button I use JS to edit the metadata in the file that the line represents. This is all working but....

Dataview doesn't always see the changes when I navigate away and then back to the page with the dataview! I can't yet find a pattern but somethings I notice..

1. If I manually edit the Yaml at the top of the page, then navigate back to the page with the dataview view - the view updates correctly
2. if I click the button, then navigate to the edited page, then back to the page with the view, dataview doesn't always update!
3. Somehow... event closing Obsidian doesn't do it, almost as if there is a file cache being written that dataview is using.
4. As stated above neither option given to dump cache, or refresh the blocks does the trick.
5. I am using await app.vault.modify(file, newFileContents); to trigger the update to the Yaml
6. I have investigated the altered Yaml and it appears to be correct - and my linter is showing correct Yaml, if it's incorrect it's red.
7. Somehow!!! if I edit the source page for the metadata and navigate back to the page with the dataview, the results are then updated BUT!!!! if I navigate back to the page with the metadata and MANUALLY undo those edits, then finally navigate back to the page with the dataview - it's reverted BACK to the wrong value!!! It's like an index is created on a file contents hash, and since I modified back to the original file hash, it's again picking up the old index value - which makes sense I suppose though I'm wondering then how those old entries are getting cleared.

I'm looking for more ideas and things I can try. Any magic buttons I can call like DV.UpdateIndexForPage(path) or something like that, which I could call after app.vault.modify(file, newFileContents);

Quick Update: I just added "Metadata Menu" to my vault. I can use that tool from the page with the dataview to edit the metadata of the page the view is displaying, then manually refresh the view, and it works just fine. That leads me to believe that I am not triggering something properly when I manually make changes to the metadata of an alternate page - which "Metadata Menu" appears to do correctly. I will explore their codebase to see if I can determine what they are doing to properly edit the metadata in a way that allows dataview to see those changes. I'll report back if I find anything.

[TheAtomAnt]

I think I know what happened. Not 100% sure but maybe this will help someone else.

1. I have just switched to using the Metadata Menu API - it has abilities to update the frontmatter, and no reason to reinvent that.
2. When trying to update the frontmatter, with or without Metadata Menu API, it seems that if you want to update a bool field you MUST pass the bool value in as a string... so no false values. You must use "false". After making that one small change my code started working and even the dataview started updating correctly. I can't really imagine what in the world is causing such odd behavior with the dataview, but while debugging with Metadata Menu and their API, I learned that I must use strings for the values of the front matter updates, and then internally it will deal with converting the values correctly.

Although I think it'd be neat to better understand what was going on with the dataview, I'm putting this issue down and I have my code working. Thank you to the Metadata Menu folks for adding an API to their plugin! Thank you for the folks working on DataView for their awesome plugin for Obsidian.