Hi All
I want to print a Order Tag for a free item with price 0.0 on slip, but issue is whenever a free item is added to order and user clicks print the SAMBAPOS crashes/stops respoding.
It only happens for free item in Order Tags with Price tag 0.. I think {ORDER TAG PRICE} in Printer template fails because item price is 0 or null, but not sure how to fix this.
I am new to SAMBAPOS, can some one please point me to right direction to print Order Tag with price tag 0.0 on slip.
I have attached Screenshot of order as 'OrderTag1.JPG' and the item in question is source 1. Order tag item source 1 is crashing the SAMBAPOS software.
Printer tempate
[LAYOUT]
-- General layout
<T>Restaurant
Delivery Details
{ENTITIES}
<F>-
{ORDERS}
<F>=
<EB>
{DISCOUNTS}
[<J10>Total Gift:|{ORDER STATE TOTAL:Gift}]
<J10>Total:|{TICKET TOTAL}
{PAYMENTS}
<DB>
<F>=
<C10>T H A N K Y O U
[DISCOUNTS]
<J00>{CALCULATION NAME} %{CALCULATION AMOUNT}|{CALCULATION TOTAL}
[PAYMENTS]
<J00>{PAYMENT NAME}|{PAYMENT AMOUNT}
[ORDERS]
-- Default format for orders
<J00>-{QUANTITY}{NAME}|{PRICE}
{ORDER TAGS}
[ORDERS:Gift]
-- Format for gifted orders
<J00>- {QUANTITY} {NAME}|**GIFT**
{ORDER TAGS}
[ORDERS:Void]
-- Nothing will print for void lines
-- Format for order tags
[ORDER TAGS]
-- Format for order tags
<J00> * {ORDER TAG NAME} | {ORDER TAG PRICE}
[ENTITIES:Table]
-- Table entity format
<L00>Table: {ENTITY NAME}
[ENTITIES:Customer]
-- Customer entity format
<L00>Ticket No:{TICKET NO}
<J10>Customer:{ENTITY NAME}
Thanks
Syed
4 answers
We'll release a fix (V3.0.30) for order tag printing shortly. Please let us know if it will solve your problem or not. Thanks.
OrderScreenShot-
'OrderTag1.JPG#sthash.HpEyXzSD.dpufOrderTag1.JPG#sthash.HpEyXzSD.dpufOrderTag1.JPG#sthash.HpEyXzSD.dpuf
Thanks emreeren for your quick response, I was still proof reading my post and got response excellent.. Can you please confirm, is it Database fix or code, and when it will be released?
Regards
Syed
for order tag printing shortlyemreeren
I confirm this issue is now fixed in new release (V3.0.30)
Thanks emreeren for quick fix on this issue.