Round Function

vinsnash

There is an 'Amount' that will sometimes contain two decimal places i.e.

Amount = 52.52

In the user guide shows this description

Returns the first number rounded to the precision of the second
number. For example, ROUND (6.738, 1) = 6.7; ROUND (6.738, 2) =
6.74

We have a dollar Amount attribute that sometime contains two decimal integers i.e 6.74. This needs to be rounded to the nearest whole dollar. I've tried "Amount=ROUND(Amount,0)" but the result appears as 0. How do I round Amount to the nearest whole dollar?

Vins Nash

tford

Have you tried using a different attribute for the rounded value?

Instead of: Amount=ROUND(Amount,0)

Use: "AmountRounded=ROUND(Amount,0)

vinsnash

That didn't occur to me but I'll try it now and report the result.

Thanks

vinsnash

Didn't make a difference. Perhaps because I have the ROUND function within a CREATE?

I use the exact same syntax in a rule without CREATE and the rounding takes place as expected. In the following case it doesn't work. Pending.Amount will contain the number with no rounding if I remove the ROUND statement. With the ROUND statement Pending.Amount ends up as zero. Every thing else ends up as expected in either case, with or without ROUND.

IF NSCPers.Reenroll WAS CHANGED TO 'Yes' AND EXISTS FeeTable WHERE (FeeTable.Type=NSCPers.MemberType) Then
FIND FeeTable WHERE NSCPers.MemberType=FeeTable.Type
CREATE Pending WITH
Pending.MemberType=NSCPers.MemberType,
Pending.Type=NSCPers.MemberStatus,
Pending.SocialSecurityNumber=NSCPers.SocialSecurityNumber,
Pending.LastFour=CHARS_FROM_RIGHT(NSCPers.SocialSecurityNumber,4),
Pending.UnitCode=NSCPers.UnitCode,
Pending.Amount=FeeTable.Amount*NSCPers.MonthsToEnroll,
Pending.Amount=ROUND(Pending.Amount,0),
Pending.Date=CURRENT_DATE,
Pending.LastName=NSCPers.LastName,
Pending.FirstName=NSCPers.FirstName,
Pending.BirthDate=NSCPers.BirthDate,
Pending.ExpireDate=NSCPers.ExpireDate,
Pending.Rank=NSCPers.Rank,
Pending.Paid = 'N',
Pending.Type='R'

BenchmarkDan

I used to use FLOOR and REMAINDER for this type of thing. I don't see a REMAINDER FUNCTION.

Maybe try,

a = 5.67

thefloor = FLOOR(a) (returns 5)

if (thefloor +.50) < a
answer = thefloor
else
answer = thefloor + 1.00

tford

Not sure how you can say it didn't make a difference. You didn't try my suggestion in the what you showed above.

Pending.Amount=ROUND(Pending.Amount,0),

Humor me by making another attribute in Pending BO and try:

PendingRounded.Amount=ROUND(Pending.Amount,0),

OR try:

Pending.Amount=ROUND((FeeTable.Amount*NSCPers.MonthsToEnroll),0)

vinsnash

Tom, your 2nd suggestion works like a charm. Perhaps the ROUND on the result of the calculation is executing to quickly to have an affect? What works works so I'm not complaining.

I owe you one.

Vins Nash

tford

When you were using: Pending.Amount=ROUND(Pending.Amount,0)

You were just going in a loop with an attribute based on itself.

rocketman

If Pending.Amount must ALWAYS be an integer then you code should simply be

Pending.Amount=ROUND(FeeTable.Amount*NSCPers.MonthsToEnroll,0)

tford

Rocketman .. that's what he did per my suggestion a couple of entries earlier.

vinsnash

Oddly enough it works in a rule when not used in a CREATE. Before I was asked by the bean counter to provide a transaction history I used this rule attached to the object NSCPers.

IF NSCPers.Reenroll WAS CHANGED TO "Yes" AND EXISTS FeeTable WHERE FeeTable.Type = NSCPers.MemberType

FIND FeeTable WHERE FeeTable.Type = NSCPers.MemberType
NSCPers.AmountPaid = FeeTable.Amount*NSCPers.MonthsToEnroll
NSCPers.AmountPaid = ROUND(NSCPers.AmountPaid,0)

ELSE REPORT ERROR ........

That always worked.

There is a definite need for an "AwareIM For Dummies." Maybe a published compendium of the solutions brought to light by this forum would be a start.

Vins

rocketman

Tom - my apologies,

That's the problem with speed reading whilst trying to watch a football match on a Saturday night

tford

No worries .. just wanted to clarify for any future readers of the thread.