I am changing a date field in a database connected data source using the table component. This sometimes produces a bug where the date is not updated in the database, or in other apps, or in the same app after refreshing.
Suppose we have three dates: A, B and C. If we change the date from A to B, then back to A, the last change is not persisted. If we change the date from A to B, then to C, then back to A all changes are persisted.
A → B → A This does not work. The value B remains in the database.
A → B → C → A This does work. The value A is reflected in the database.
Have you been able to reproduce this in e.g. a standalone app? Given the description, I am unable to reproduce this. It might be that, due to e.g. a vast amount of dependencies towards that update, the side-effects is causing the update to take too much time, resulting in the UI allowingto set the date back before the first update succeeds.
Would be nice to know if it reproduces in a standalone case, and if not, some analysis on what is happening in the console log related to side-effects/data source recalculations etc.
Trying to get som priority on this one, as it sounds like a regression error (it has not been like this forever I believe).
Note: This occurs whenever you edit a date in a table to a new date, and then back to the original. The new date remains. You are still allowed to change it to a new date, and then another new date. Nevertheless, this issue should be fixed pretty soon.