Using inspiration from https://community.appsheet.com/t/dynamic-view-name/14220
I have an action A attached to a column in table X that is a grouped action with sub-actions B and C:
B) write a text field in a table Y for storing “titles” to include information about the selected row
C) “go to another view within this app” which is a Table view of another table Z. This Table view has “Display name” set to a lookup in table Y to retrieve the “context sensitive title”.
Problem: select action A, B queues up the write to the server, C gets executed and we enter the new view immediately. However the view’s title is set to the previous setting. After a while the write goes through to the server and is synced back to the app at which point the title changes.
Desired solution: have the application’s copy of the data change immediately, and let the write sync to the server in the background
Higher level question about reasonable expectations of writes: I expect writes to show up immediately on the client side when made to any table. These writes should affect all formulas and expressions immediately. Writes are flushed to the server in the background. I am not trying to get at how it currently works but rather how should I expect it to work, ie. what is considered correct functioning. Are my expectations about correct functioning reasonable or is there a reason why they are not reasonable, please explain?
This FR is also about round trip writes affecting the UX: https://community.appsheet.com/t/form-saved-data-takes-round-trip-before-details-view-sees-it/41156 which I have initiated a repro case with email@example.com about.