Pretty sure that this is a bug, but when you don't 'enter' a table value into the table and click save immediately, it says it has detected the change (2 changes) yet the data doesn't flow through.
I have attached two screen recordings for clarity, I know it isn't the query which is the issue.
One with the bug:
And the expected behaviour: not sure why it goes to zero at one point...
I have seen this before.... It might be, if I recall correctly, the focus when clicking save without hitting Enter..... so, you could try using Debounce in the event handler that is executing the bulk save query - give it a value of 1000 (ms)
Hi @Marcus and @ScottR, I can confirm this is a current limitation of the table component. We suggest training our end users to press either tab or return after every change to prevent this unexpected behavior.
On the other hand, I would love to hear if adding the debouncer worked for you; this would be a great workaround for the customers who have reported/requested this feature.
I can confirm that the debounce works! I found you could put the debounce as low as ~100 ms and it would still function as intended, @Paulo could it be placed on the Retool side an automatic debounce to prevent this issue?