Any idea why Ticket Number skip?
Did you merge tickets?
EDIT: Sorry not merged but move?
It happens if orders moved to new tickets and original ticket is left with no orders.
Hmm, I think it left 0 amount ticket after merge.
That would do it. It does this by design so you dont have empty value tickets… the new ticket takes on the ID of the old empty ticket once its closed and saved. Old empty ticket just closes.
I tried move table but ticket number have not changed (well, it just entity change, make sense to still have same ticket no). I will tried move orders in sec.
Edit: Move some orders current ticket (16389) to new ticket (16392). Then, merge it back ticket number change to 16392 and leave 16389 and 16392 empty ($0). I still see zero amount tickets.
I still can’t find how this skip. You know now we can’t move all orders in the ticket to new ticket right. After @Jesse split payment method.
I HAVE same problem and is really big problem because i use ticket number as a
legal accounting document and have really big problem with tax, how use a diferent number or avoid ticket skip? is urgent because is on work the restaurant and cant back to old system. need a unique no skip number.
- PLEASE HELP IS URGENT *
ok i think how resolve if can modify number on transaction id and use this to invoice/factura number… how change the number (or just modify on sql?) and how identify in print template this item.
You should not modify those numbers in sql you will break something. So is {TICKET ID} not good enough?
{TICKET ID} is what you should use for accounting not {TICKET NO}
just need a number never skip… TransactionDocument_Id is a number i review is identity and continuos. thicket id change and skip numbers and is a big big problem.
ok i review and noot work because Transaction Document Id is for every transaction, not only sales, and if add a inventory operation or someting modify this id, im frustrated with a big problem and unknow how make a id unike and correlative to every operation sales… 
Skipping canceled tickets is one thing but how can you expect it to skip all void tickets which have been created submitted then voided, do you expect that ticket number to get cleared and reused?
You tickets would not be in sequence which tax people would not like as much as skipped.
I doubt that your financial system does not take in to account at all that a ticket can have a zero total (voided)
Any system would work like this!
If you used pen and paper on a duplicate book, what would you do if you made a mistake? Chuck the invoice but the void/mistake duplicate would still be in the book marked as void.
The skipped tickets are still recorded!!! Which is what tax people look for. Ticket Id is sequential and no skipped tickets just some tickets have 0 value
i try to use Number generator (i think is the best solution to avoid skip tickets) but can’t configure, i follow text instructions but witout print screen unknow why not work. i have a big legal problem if not resolve today this problem.
i just wait the police to go jail
{TICKET ID} and {TICKET NO} are different things.
The {TICKET ID} is created automatically and is always sequential. This is handled by the SQL DBMS. It should never “skip” a number. However, there are some very rare cases when it might do so, which is really a glitch in MS SQL…
The {TICKET NO} is created by the Ticket Number Generator, which is part of the Ticket Type definition/configuration. For the most part, it never “skips” either, but you will have empty Tickets that are a result of Moving and/or Merging Orders/Tickets.
So take your pick. Use whichever Tag suits your needs. You can use either Tag in your Reports and Ticket (Bill) Templates.
If you really want to use another Number that you have complete control over, you could use a Program Setting.
1 Like
OK {TICKET ID} aparently The solution, just try to change in database the number because need begin with a specific number and can’t change by table relational and index. but in working now…
If your asking a question like that I strongly suggest you DO NOT change anything in database.
Values like that are relational and if you could changing your potentially corrupt or at least screw up your database.
Ticket ID is referenced in probably a dozen tables which link all the data together.
i try now but Ticket ID (in database is TransactionDocument_Id) is not work fine because when merge couple of tikets add a new TransactionDocument_Id and in database not skip number but if use this make a skip in bill/invoice and is the same problem… i try other options if the police not come before
Ticket id and transaction document Id are not the same thing, at least to my knolage,
Am stifling to follow, is you issue ticket id or transaction document???
If you so worried about the police, which personally find doubtful, follow up on WA sugestion about generating you own unique reference using program setting value and ticket tag, has been discussed many times of forum by people with similar consern as you.
They are not the same thing. Check the [Tickets] table …
DBfield Tag
------------------------ --------------
[Id] {TICKET ID}
[TicketNumber] {TICKET NO}
[TransactionDocument_Id] (no valid tag)
Now you might be looking at this and wonder why the [TicketNumber] is jumping around. This is because I have more than 1 Ticket Type, and they each use a different Number Generator. I did this to keep Staff and Quote Tickets out of regular Customer Sale Tickets.
Personally, I use {TICKET NO} ([TicketNumber]) as do most others.
ok i serius now… in resume i need a unique correlative,not skiped diferent of ticket id/no because is a legal document (invoice/bill) and it’s not possible skip any number by tax law, this number is “created/asigned” when full payment its done (one document by one payment complete). you can sugest the best option to make this operation? i review many many help forum but nothink have a solution finished, unknow if just my have problem with this because many countrys tax law need this type of number correlativve.
i try to pay for support but all say “it’s really easy just do youself”… and i have 12 days without a solution …
Ok, here you go …
Voiding Orders, Moving Orders and/or Merging Tickets should not affect this number, which I have named TID and applied it to the Ticket as a Ticket Tag, accessed by {TICKET TAG:TID}. This is because the TID is generated and applied to the Ticket when the Ticket is PAID in FULL.
##Ticket Tag
##Actions
##TID Update Invoice ID
[Update Program Setting](Action)##
| Action Name: | TID Update Invoice ID |
| Action Type: | Update Program Setting |
| Setting Name: | TID |
| Setting Value: | [:TIDvalue] |
| Update Type: | [:updateType] |
| Is Local: | False |
##TID Assign Invoice ID
[Update Ticket Tag](Action)##
| Action Name: | TID Assign Invoice ID |
| Action Type: | Update Ticket Tag |
| Tag Name: | TID |
| Tag Value: | [:TIDvalue] |
##Rule
##TID Update and Assign Invoice ID
[Before Ticket Closing](Rule)##
| Rule Name: | TID Update and Assign Invoice ID |
| Event Name: | Before Ticket Closing |
| Rule Tags: | |
| Execute Rule if: | Matches |
Remaining Amount | Equals | 0 |
##Actions (2):##
TID Update Invoice ID
Constraint: (none)
| TIDvalue: | 1 |
| updateType: | Increase |
TID Assign Invoice ID
Constraint: (none)
| TIDvalue: | {SETTING:TID} |
##Mappings##
Mappings
| Terminal | User Role | Department | Ticket Type |
* | * | * | * |
You can have this print on your Tickets using: {TICKET TAG:TID} …
2 Likes
ok this is exactly what I needed, works perfect, just a little problem (i workin on) because when print invoice the " Invoice: {TICKET TAG:TID} " print first time in blank (null) and after the reprint (after finish) print with number (correct numbert and all ok), I think is in rule"print bill" the first action is print and after make the other flow instructions… working on
It won’t generate TicketIds until ticket is closed. So if you press print before ticket closed it won’t show.