The reason this setup is written this way is because theoretically someone could pay with multiple types, multiple times before the Ticket is fully paid. Ideally, we would want to be able to store all tenders separately, something like this:
I know it might look ridiculous to use so many Payment Types on a single Ticket, but it does happen, even if only rarely. So it would equate to this (or similar):
I am not well-versed in Custom Report Tags, so I canât really comment - you would need the ability to check the Tag name to see if it âcontainsâ certain characters, similar to the LIKE %name% function in SQL.
Using SQL, you could theoretically parse out the Tags using LIKE and SUBSTRING() functions, but I havenât looked into it - plus the Tags are stored in JSON format which makes things much more difficult⊠this is where Custom Report Tags excels over SQL, because @emre has designed it in such a way that it makes reading Tags fairly simple in comparison.
So for example, if you paid with Cash, the Ticket Tags for CCtype and CCdigits would have no value, and when you use the square brackets, the entire line will not print.
The same would apply for Change due - if the value is 0, nothing will print when enclosed in square brackets:
[<J00>CHANGE:|[=F(TN('{CHANGE TOTAL}'))]]
You wonât be able to avoid printing the Tendered Amount however, since it will always have a value.
Is there a way to add text when there is no value? For example if change was zero and tag was in sqaure brackets so it didnt print could the words NO CHANGE DUE be added instead?
The thing is custom reports are custom. We do not know what your report syntax looks like unless you show us. You can do anything with custom reports. Show us what syntax you used and I can show you options for results you wanted. I can also explain why your report turned out like that when you wanted it to look different.
i have set up everything according to the tutorial, but just one question, the ticket tags at the start, wat is the setup for them?? and the mappings? i removed the mappings and now the whole POS freezes.
i have added the mappings to each of the ticket tags, but it still freezes when i want to make a Credit Card Payment. and it doesnât even ask for the CCinfo at all
What ticket tags at the start? What do you mean? All ticket tags appear UNDER the ticket
What mappings have you removed? From what rules or buttons?
If it freezes and doesnt ask for CC info you have configured things incorrectly. Im not at my pc but i suggest you go through step by step and check everything again to find your error. This will also help you learn about samba and since we dont know what youve changed and how going through the tutorial and checking your setup will help
if i want to change the mode of payment from CC to Cash after settling the ticket with CC first. How will i be able to clear the tendered type tag (PMT ) from ticket.
and since we dont know what youve changed and how going through the tutorial and checking your setup will help
