Hi @Bernd_Strehl Thanks for reaching out! I'm looking into this internally.
Since you mentioned this is a critical app, would it work for you to add an event that clears the changeset until we sort out what changed in the product?
Hi @jg80 Thanks for checking in! Unfortunately, we don't have a fix yet. I don't have an eta for this one, but I'll post here if I get any updates internally
I might be using it wrong, but this still doesn't work (retool 3.24.9)
When i don't use clearChangeset() it updates the data in the table, but it doesn't clear the changeset.
When I call clearChangeset() the query errors out because the changeset is empty.
I tried building around this issue, by disabling saving if the table is fetching or if the changeset is empty, but it's telling me that false or false is true.
Again, I might be misusing it, but false or false should be false, not true.
Hi @dakes I believe it's evaluating the string "false || false" as true. If you put the whole statement in double curlies {{}} it should be read as false:
We still have an outstanding bug where the table changeset doesn't clear on save when its datasource is a temporary state. Is your table populated by a transformer?
What is the run script event doing on save? If the run script event is where the clearChangeset code is, it will run at the same time as table1_save and cause an error. I'd suggest moving your clearChangeset code to happen on success of table1_save
Another note is that if you have a table populated by a query, rather than a transformer, the changeset will not clear unless you trigger a successful update query and then trigger a refresh of the table (or trigger a clear changeset event).
I'm having a similar issue.
I've tried triggering the clearChangeset as an event onSuccess of my updateQuery. changesetObject appears to be cleared, which changesetArray is not.
Hmm, are you seeing this in an existing or relatively new table? I see that we had another user run into the same bug. The temporary fix was to delete & recreate the table