Hi @axme ,
I have replicated your issue.
first, I can’t find how to reset dropdown to be select, it may have something to do with browser’s cache
second, if dropdown=select, then its value comes from cache, so it is better to make variant=“none” for every variant id (I have not implemented this)
Here is the rundown,
Here is the variants collection
Menu master collection,
Order menu item, this one after rundown,
I have used 3 collections,
- variants collection which include variant id for filtering
- menu master for showing on order screen and have variant id for dropdown
- order menu item, for transaction
This is regading issue #2 above, if we don’t select anything (dropdown=select), when we update with its value, we update with its previous value (its cache), which I think this is qualify as a bug.
So to make a workaround, I suggest to create “none” in every variant id (in variants collection), hopefully user will select it rather than (dropdown=select),
or maybe you could play around to alert user if there is dropdown which is select.
try modal screen as alert and make switches with input field, maybe this could work.
ohh, when I save, i try multiple updates.
1st update, no conditional
2nd update, with conditional
3rd update, with conditional
I use form inputs, not from collection, this thing can easily slipped our mind, as they looked like almost the same.
It is hard to explain without standard terms, this one is very specific case.
Alright, happy fighting…