SambaPOS will install SQL Server LocalDB by default when there is no database engine selected. LocalDB is 33 mb single user database and it is easily upgradeable to SQL Server Express. If you need to install SQL Server CE (2MB) engine you can enable it on Install Wizard > Select Components screen. In this case you need to uncheck SQL Server LocalDB option. If you already installed SQL Server CE on previous versions SambaPOS automatically disable LocalDB selection to prevent unneeded downloads.
With this release Ticket Lister Widget have Expression and Filter settings.
Expression is used while preparing ticket selection SQL. In expression part you can filter tickets following Expressions.
TicketDate is Today checks if ticket Date equals today.
TicketDate is Today+1 checks if ticket Date equals yesterday. You can increase number to check future dates or you can use negative values for past tickets.
You can use smaller or greater operators and use multiple expressions such as TicketDate > Today+1 and TicketDate < Today+2
If your expression is not suitable to translate to SQL you can use Filter setting. After SambaPOS reads tickets from database it applies filter.
Use IsTaggedWith("<tag>") to filter tickets tagged with <tag>.
GetTagValue("<tag>") is "<tagValue>" to make string comparisons.
GetTagNumericValue("<tag>") > 5 to make numeric comparisons.
GetTagDateValue("<tag>") is Today to make date comparisons.
There are much more possibilities so please ask us your specific filtering needs.
Some Lists at Management Screen supports searching by item values. For example you can search products by barcode wih barcode:123 or barcode=12345678. If you need partial search use : character and = for exact match. There are more options such as searching by Group Code. Since these are dynamic search values all options are not listed here. Please ask us if you need specific searches.
More Ticket Actions module includes Update Ticket Date action. You can use action parameter query feature to display a dialog for changing dates. [New 4.1.7] Asking Action Parameter Values
i am using the kitchen display set up created by john,
according to the current set up, once the order submitted, it is displaying in kitchen entitites.
with your new release, i manage to exclude the drink out from kitchen entities. however, i wanna further improve as ur new release allow ticket lister widget show in different grouping ie, appetizer, main, dessert. i want my kitchen to do appetizer first and tick it off individually instead of the whole ticket.
I found workaround by requesting the cashier to change the order status to delivered individually in the ticket screen. however, it doesnât remove item in the kitchen screen.
so i thought, that might be something can be used by order filter/filter function to filter the displayed item according to order status or something?
alternatively, would be great if kitchen is able to tick off each item by item individually.
Ticket lister displays tickets and filter & expression features filters tickets. Youâll filter out unwanted orders by printer template features like youâve did for drinks. I couldnât understand how your state flow works as I donât remember Johnâs setup from mind but I think there should be a non-delivered state for orders so you can display only non-delivered (served) items.
Is there a way for ticket lister widget to filter by entity? Specifically tables?
I have tables called âTake Awayâ and âPickupâ and I use them to take orders.
I would like to one TL widget to show all unpaid Take Away orders and one TL widget to show all unpaid Pickup orders.
You canât filter tickets by entity name but you can filter tickets by ticket tag. So tagging tickets automatically when you select related entities might be a solution for you.
I followed instructions on that post. Was able to set one tag successfully.
However I have 3 tags that I need to set, depending on the table selected (Takeaway, Pickup , Delivery)
@srijit in the future create a new topic and select the correct category for the version your using. It can lead to confusion if you resurrect topics that are almost a year old to ask a question.