I think i’ve got a big issue now after SambaPOS version update. Currently using 5.1.61 Beta.
Automation Command executed rule on Automation Command Buttons doesn’t seem to work! I had delivery charge setup using the same kind of setup:
Automation Command ‘Delivery Charge’ with values 20,40,60,100,Free
Automation Command Executed rule to set delivery charge.
This was working fine, tested multiple times on v5.1.59. This does not work any more.
Its an urgent situation now as we are launching officially this coming monday. We upgraded the system to be able to work on some web services to integrate with the website.
I checked with v5.1.60 on my test computer and that seems to work fine. Unfortunately, after upgrade to v5.1.61 i have already done some changes, so reverting back to v5.1.60 will make me lose some of my work.
To be quite honest you probably shouldn’t use a beta version in a working environment unless you are 100% sure it will work for you… If some hijf isn’t working in 1 version, assuming you have a backup, revert to an older version by uninstalling latest one and installing the one that works. Then use the beta to test till the issue is fixed then upgrade your working environment
yeah it seems strange to have this functionality broken. However without changing anything, using 61 even on my test machine failed using the old functional setup that works at 60. So im a bit lost.
Automation Commands that do not submit a CommandValue seem to work fine. But all Commands that have a value to submit fail. Nothing was changed on them at all… Got it to work and moved on to the next thing…
Have sent my DB to emre in a PM, and hoping he can figure out if its a bug in the software or my code. If all else fails, will do the Revert version. Thanks!
Alright. copied the DB to my test machine, changed DB version back to the one corresponding to my install here (Table VersionInfo, deleted all entries that were higher than the version in the version.dat file).
Ran it on v5.1.60 works like a charm. Even the promotion bit is working.
So i think i can confirm this as a bug in 5.1.61
Haven’t seen any replies from anyone yet, so here is my planned process:
At new ticket, select Promotion. This promotion saved in a ticket tag.
On adding new order, based on the promotion selected, check the following:
• Order Item Group Code
• Order Item Quantity
• Number of Order Items already with a particular order tag (tag name promotion)
If all conditions met, add the new order with the promotion tag if valid.
Add ‘promotion price’ to the ticket(will apply the same idea as delivery charge) and make the relative orders Free.
Im currently stuck at step 2 where i need to get all this data, and then set the Order tag using a ‘Order Added to Ticket’ rule. Any pointers?
Doesn’t work for me. Cant really have promotion prices because i have sets of products under categories and the set has a fixed price. If i have 1 Salad (A category of products. Different products with different prices.) and 2 breads free with it(another category with different products and prices). So i can not exactly apply a second rate table.
Lets say a customer wants 1 salad and 3 breads. Then i need to charge for that particular salad, two breads free, and one bread to be added to the total. So i need to also keep a count on number of items in the ticket. Entity changed event is too late. Need these calculated as soon as order is added to ticket. So it has to be at order added to ticket.
Other promotions have other schemes, but basically i need to be calculating on the fly as soon as an item is added to the ticket. So, my question is what are my possible list of actions on an ‘Order added to ticket’ event ?
Turned the Promotions into products with prices and created a separate menu category.
Added an apply promotion button for the orders.
The action basically sets the Item price to 0 so the promotion product price is applied and the item gets flagged as promotion item.
The only downside is cant let the ticket total be 0 when applying this action, that makes SambaPOS crash.
Error report says attempted divide by 0. So i think as long as we follow some basic procedure we can prevent the crashes.