After updating to version 4.1.52
{TICKET QUANTITY SUM} is Not Displayed
Actual result:
Expected Result:
Total Items ordered: 3
Kitchen Template:
[LAYOUT]
– General layout
KITCHEN TICKET
Date:{TICKET DATE}
Time:{TICKET TIME}
Operator:{USER NAME}
{ENTITIES}
-
{ORDERS}
-
TOTAL ITEMS ORDERED: {TICKET QUANTITY SUM}
-
NOTES:{NOTE}
-
I thought it was {TICKET QUANTITY SUM:X} ?
Try putting {QUANTITY SUM} under [ORDERS]
This should work.
[LAYOUT]
-- General layout
KITCHEN TICKET
Date:{TICKET DATE}
Time:{TICKET TIME}
Operator:{USER NAME}
{ENTITIES}
-
{ORDERS}
-
NOTES:{NOTE}
[ORDERS]
<J00> {QUANTITY}- {NAME}
{ORDER TAGS}
<F>-
<J00>TOTAL ITEMS ORDERED: {QUANTITY SUM}
{ORDER SUM} is not {ORDER COUNT}
EDIT: Ok that doesnt work either. I will look further into it.
It was working before without any issues. something has changed on the latest update.
Well it doesnt list {TICKET QUANTITY SUM} as available it says {TICKET QUANTITY SUM:x} I am not sure what x would represent.
If we knew what to put for the X it would work. {TICKET QUANTITY SUM:Orders} produces a 0 So its working we just need to know what x should be.
Ok so I tried {TICKET QUANTITY SUM:Burrito} Burrito is my product name… and it worked… now thats not very efficient lol. Cannot enter EVERY product name into there lol. There has to be more options for x. It would be very tedius to enter EVERY product for x. I tried Category names… and it did not work.
Maybe there is a wildcard to enter that covers all products. I have yet to figure it out though. @emre would need to fill us in it looks like.
As I can remember I’ve didn’t recently changed how {TICKET QUANTITY SUM} works but if you’ve upgraded from an older version it is possible. {TICKET QUANTITY SUM:X} expects a menu item name parameter and also an optional state. By using it as {TICKET QUANTITY SUM: } it should generate the desired output. There should be a space after colon. I’ll also enable parameterless version for next update.
In the ticket (printed notepad screen) says {:TICKET QUANTITY SUM} , note the: inside brackets…
could that be your problem??
G.
Thanks Emre,
{TICKET QUANTITY SUM: } fixed the issue.
I have been using {TICKET QUANTITY SUM} up to version 4.1.37 without any issue. I did carry out upgrade from 4.1.37 to version 4.1.52 yesterday and then noticed the issue.