Yes it could have… or if he recently added the ability to remove an Entity like that it might have came up. But 99% of people do not remove entities like this and then cancel orders… typically you just cancel orders and close ticket and it updates the entity to available.
We can fix this if you think you would be removing entities before canceling orders. We just need to find a better placement for the Available state since you do not have an Entity to update anymore./ The most logical and first thing I think of is Ticket Closing but this could impact other things if we dont constrain it right.
Well I wouldn’t normally do that in production, I was just testing things when this started happening. But of course it would be better to have it as fool-proof as possible.
Did you reproduce this on a new install or also on @emre’s database?
If not, I can do a fresh install and see if we already have it there, but that’s going to be for tomorrow then (it’s almost five in the morning here).
Fresh database install. You can load fresh basic databases without reinstalling SambaPOS… just change Local Settings to a new DB name and it will create one. Good little trick for testing.
You can also enable Multiple instances of SambaPOS in the Settings.txt file and load up 2 different databases at same time. This can be automated through rules I sometimes have 3-4 databases and 3-4 SambaPOS instances open at same time for testing.
For example on my test system… If I log in with a specific Username that I setup for a specific DB. It loads that database then displays a popup telling me its loaded… I press OK and then just login with Admin and im in the new database.
When I logout it loads the previous Database again. So my flow is I have 3 test databases Im using… i have 3 specific Usernames for each database. I load a Samba Instance and login with USER A it loads Database A. I load up a 2nd instance of Samba and login with USER B it loads Database B. If I logout of either test database it loads the default Database that I want.
Not so useful for production but its wonderful for development.
Yes you use that… And since you have to logout for it to change I use an ASK question action to display a popup saying BLAH Database Loaded Please login as Admin and when I press OK it logs out and then i simply just login as Admin.
LOL, I had this happen too during testing. I knew something was wrong, but didn’t look into it, since it wasn’t a big deal. In normal operation, it would be rare(ish) to have this flow, so you would never see the issue. I agree though, we need to set something up to correct this issue.
It doesn’t have anything to do with this Topic or the implementation of this Discount - it is specifically related to changing an Entity, then clearing the Orders as you and @Jesse have worked out already. it’s not just Customers, it’s Tables too (or any Entity that has State colors).
What we need is a way to capture Entity Removed so that it’s State can be updated, but only if the Entity has no Ticket assignments.
Select Entity (Customer or Table), for illustration, pick Table … at this point, the “Select Table” button on the left side should display “Change Table” but it still incorrectly displays “Select Table”
Select Entity again (choose a different Table)
Cancel the Order
Select Table - here you see the last selected table from the above
sequence is still Orange - but it has no Ticket or Orders.
Hi, I did exactly what you have done. I made account Stuff, so the stuff will use percent discounts of the products, but when I tried it, nothing happens. Should I have to make something more to connect the discount rules and actions to the Stuff account?