Validate numeric form field entry

technopak

hi,

I've come across a strange one -

I have a BO form with fields for entry of numeric attribute values. I've noticed that if a user inputs anything except a number in those fields, that the system returns an error message and the creation of the particular object fails completely - the user must re-commence creation of the record.

Can someone suggest the best way of validating such form field entry ? I can't seem to get a rule such as the following to work. It never reports an error.

If NOT (Object.Deposit BETWEEN 1 AND 1000000) THEN
REPORT ERROR 'Value of Deposit is invalid'

Sorry if this is obvious, but what am I doing wrong ?

As usual, thanks in advance 🙂

Peter

e5n_devildog

Pete,
Try the format option of the attribute. It should limit the allowable text to the field. Also there is a range specification at the bottom of the attribute screen.

Something like # as the format then specify the range below.

e5n_devildog

Sorry forgot to mention. I can shoot you the bsv if you need me to. Just give me an email.

tford

Peter,

You must be trying to input into a PLAIN TEXT type attribute rather than a NUMBER type attribute. If you use a NUMBER type attribute, AwareIM will NOT allow anything but numbers to be input. If the user tries to type in letters, they will not even appear on the screen.

technopak

Thanks Devil Dog,

Your post is a big help.

I changed the format on my Deposit field to # as suggested (it had been #.00) and now at least the field only accepts numbers. So that is an improvement.

I'm quite baffled about why the field should accept non-numeric input when the format was #.00

Any ideas ?

Peter

technopak

Thanks Tom,

My issue seems to be about the #.00 format allowing any alpha character input.

I don't know why it should. I'm using build 1188, wondering was there a bug or something ......

Peter

tford

Peter,

That sure looks like a minor bug. I'll send a bsv over to support to document it.

e5n_devildog

What about using #.## format?

e5n_devildog

Nevermind I see that #.## still gives the issue.

technopak

Thanks Tom and Devil Dog,

At least I'm not losing my marbles 🙂

Even using #.##, the field still accepts alpha input.

Has anyone tried this on a later release ? Has the issue been sorted I wonder ?

Peter

tford

#.00 is an issue on build 1195. It still accepts alpha. I'm sending bsv demonstrating that to support today.

tford

My bsv to support will also show that #.## is an issue.

technopak

Thanks Tom,

I'll look forward to the next release to sort the issue so.

Peter

tazzmaxx

It must be some form of truncation of non-numeric characters that the system is doing when saving the record since:

44.A = 44
44.12A = 44.12
44.A12 = 44

Thanks for sending the bsv to support Tom.

aware_support

This behavior is a "limitation". Any number format other than "#" will allow alphanumeric input. However, Aware IM should still validate the number properly when an invalid value is saved and display the appropriate error message.

technopak

Thanks support,

As you say, the system will validate the input correctly, but the problem is as I mentioned in my original post - all data entered in the form is lost and the user must start all over again. As you'll understand, this is a big headache if there are many fields to be completed on the form.

If it's a limitation, that's fine.

Can someone tell me why the validation rule which I tried originally fails -

If NOT (Object.Deposit BETWEEN 1 AND 1000000) THEN
REPORT ERROR 'Value of Deposit is invalid'

Does alpha input qualify as being between 1 AND 1000000 ?

Perhaps the system validation of the #.00 format field occurs before the rule of the object ??

Peter

aware_support

What does the LogViewer say?