Nope. So I just removed Round Down from the calculation selector so only Auto Round Up is active.
If I have 2 items @ $2.98 the total is $5.96 - no rounding to $6.00.
With Round Down in the calculation selector, it will round down to $5.95.
Sometimes we will only Round Up or Round Down, not both. And general retail practice here is to round down.
OK. I see. Since 5.95 is nearer it skips. Maybe I can add more calculation types to always force it to round up or down.
I’ve impemented Round Ticket Total Exactly calculation. If you enable Decrease Amount that always Rounds down. If not it Rounds up.
I need to make use of this great feature as well, mainly when customer present a discount voucher i.e 20% OFF. Sometimes we end up with this:
We don’t use pence, our minimum is 0.05 Pence. So Ideally I would need to round down to £4.75.
I experimented in training mode the Autoround.zip but this was rounding a perfectly fine 5.95 to 6.00, see:
Is it possible only to round when necessary?
Okay solved.
Had to change the calculation types rate amount to 0.05.
It seems you found a different way to use Training Mode. Very nice
Training Mode, is a amazing feature. If I’m doing any changes to rules or experimenting I do it in training mode 1st
Hi @emre, i was testing the Auto round calculation rule with and come across following issue when applying Discount.
Below are my settings
Auto Round Up: rate set to 0.05
Auto Round Down: Rate set to 0.05
if i add 1% discount it does not calculate Auto round figures as expected. same for 4%,6% and 9 % as per below table.
Did you accidentally disabled Decrease Amount setting for Auto Round Down calculation?
no, i have also tested with Enabling Decrease Amount setting for Auto Round Down calculation. it did not make any difference. With Decrease Amount enabled, it should have decreased the figure, which did not happen.
How did you configured Calculation selectors ? Are you using Import file?
i used the import file option ( AutoRound.zip (700 Bytes))
So how calculation selectors configured? Does it contains both calculations (Up and Down)?
@morshed1 please double check Decrease Amount setting enabled for Auto Round Down calculation and Log off / Log in to clear possible caches. I’ve imported it to a clean database and seems working fine.
Are you doing this on a open ticket that you had on your system before you implemented the rounding feature?
Try creating a new ticket and then test how the rounding works. I don’t think it works on tickets that were created before you implemented the rounding feature, I had a similar issue.
That’s right. As a general rule no changes on calculations (configuration) should alter past tickets.
Thanks @emre, @Isaac. its working now as it should. This is what i have done… i have deleted all records/transction from sql database. enabled Decrease Amount setting for Auto Round Down
and re tested and now it work.
@emre, can you look into below error message. i receive below after clearing the sql database using (V4_dtrans) when trying to load SAMPOS. Have had the crashing issue couple of times now.
[General Info]
Application: SambaPOS
Version: 4.1.27 BETA
Region: en
DB: SQ
Machine: MORSHED-PC
User: Morshed
Date: 29/03/2014
Time: 17:35
User Explanation:
[Exception Info 1]
Top-level Exception
Type: System.Threading.AbandonedMutexException
Message: The wait completed due to an abandoned mutex.
Source: mscorlib
Stack Trace: at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(TimeSpan timeout, Boolean exitContext)
at Samba.Presentation.Bootstrapper.InitializeShell()
at Microsoft.Practices.Prism.MefExtensions.MefBootstrapper.Run(Boolean runWithDefaultConfiguration)
at Samba.Presentation.App.RunInReleaseMode()
[Assembly Info]
Samba.Services, Version=1.0.0.0
mscorlib, Version=4.0.0.0
System, Version=4.0.0.0
Microsoft.Practices.Prism, Version=4.0.0.0
WindowsBase, Version=4.0.0.0
Samba.Infrastructure.Data, Version=1.0.0.0
PresentationFramework, Version=4.0.0.0
System.Xaml, Version=4.0.0.0
Samba.Presentation.Services, Version=1.0.0.0
Samba.Infrastructure, Version=1.0.0.0
FluentValidation, Version=3.4.0.0
Samba.Domain, Version=1.0.0.0
DevExpress.Xpf.Grid.v13.2, Version=13.2.7.0
PresentationCore, Version=4.0.0.0
Stateless, Version=1.0.0.0
System.Core, Version=4.0.0.0
System.Drawing, Version=4.0.0.0
System.Windows.Forms, Version=4.0.0.0
System.ComponentModel.Composition, Version=4.0.0.0
Samba.Localization, Version=1.0.0.0
Microsoft.CSharp, Version=4.0.0.0
DevExpress.Xpf.Grid.v13.2.Core, Version=13.2.7.0
Microsoft.Practices.ServiceLocation, Version=1.0.0.0
Samba.Persistance, Version=1.0.0.0
Microsoft.Practices.Prism.MefExtensions, Version=4.0.0.0
DevExpress.Xpf.Core.v13.2, Version=13.2.7.0
PropertyTools, Version=2012.4.14.1
Thank you…
That may happen when you re-start sambapos before it fully exits.
