Stale data error when a record value change is made and saved immediately after a record value change from a modal box · Issue #2089 · cortezaproject/corteza · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Corteza v2024.9.1 is reporting “stale data” errors when a record value change is made (and saved) immediately after (i.e., without a page refresh in the client browser) a record value change from a modal box.
Expected Behavior
No response
Steps To Reproduce
No response
Environment and versions
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Build a page layout that includes both a layout box that facilitates editing a record’s value and a modal box that also facilitates changing the same value.
Change an existing record’s value in the modal box.
Save the change made in the modal box & do not subsequently refresh the Corteza page in the client browser window/tab.
Dismiss the modal box (still without browser refresh).
Attempt to change the record’s value again, but this time in the layout box & save the change (still without browser refresh).
This will result in a notification popup reporting a stale data error similar to the screen grab above. This error is also thrown when a layout box that allows for editing foreign keys (AKA a “Record selector” field that supports multiple values) is used to change & save the field’s value before trying to change & save the record again.
Is there an existing issue for this?
Version of Corteza
2024.9.1
Current Behavior
Corteza v2024.9.1 is reporting “stale data” errors when a record value change is made (and saved) immediately after (i.e., without a page refresh in the client browser) a record value change from a modal box.
Expected Behavior
No response
Steps To Reproduce
No response
Environment and versions
Anything else?
No response
The text was updated successfully, but these errors were encountered: