I am testing what happens when updating an existing order. Therefore I click on the order and get to my โOrder Detail Viewโ. This view has an EDIT button (Prominence = DISPLAY OVERLAY) and a nested table of the items in the shopping cart.
Test:
From โOrder Detailsโ view
click EDIT > view switches to the โOrder Formโ
click NEW (under the nested table) > new interface where I select a new product and quantity (but view name hasnโt changedโฆI am basically just adding a new child record)
click SAVE > returns to โOrder Formโ interface where I was before adding the new item. The new item is now also in the nested table.
Now from โOrder Formโ I click CANCEL instead of SAVE
Pop-up โdiscard warningโ appears โDo you really want to discard? Your changes will be lost.โ
I click โDISCARDโ and my view changes back to โOrder Detailsโ
PROBLEM 1:
The added item is still in the nested table. Even if I go back to โMy ordersโ view and then return to this orderโs โOrder Detailsโ, itโs still there.
The item was never saved in the Order Details view. But I have to โSyncโ in order for the item to disappear in the nested table.
This is confusing for users. How can I avoid this?
PROBLEM 2:
I found the above mentioned issue when initially adding a Changetimestamp and Changecounter column in order to be made aware of changes to existing orders. I now realized that changes are NOT registered/counted through the changetimestamp/counter columns in the โOrderโ data table, UNLESS the user clicks SAVE on the Order Detail view. (They are counted in the โOrder detailโ data table)
That means, any changes made in the โnested tableโ by clicking on an item there or using any of the system generated โbehaviour/actionsโ are not recognized by the changetimestamp/counter in the โOrderโ data table.
It basically seems that edit made to items in โOrdersโ bypass these functions when not using the โofficalโ EDIT buttons that require a click on SAVE.
What am I doing wrong? How can I successfully track updates to orders with changetimestamp/counter functions regardless of how orders are updated?
Thank you for your advise!
I think I found the answer here. Seems to be an old problem that is awaiting some enhancements to be made by Appsheet.
User | Count |
---|---|
27 | |
25 | |
22 | |
13 | |
6 |