nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Validating a Decimal

dlukezic

Hi everyone! I am trying to use validation-regex in a text field on my DCT to check that the entry in the text field is a number with up to two decimal places of precision. It is also possible that a number without decimals will be entered. I am VERY new to regular expressions. Can someone help?

Thanks in advance!
Doreen

Find more posts tagged with

Comments

Adam Stoller

I think you want something like:

    ^(\d+|\d+\.\d{1,2})$

If '\d' syntax doesn't work - you can do it the "old-fashioned" way:

    ^([0-9]+|[0-9]+\.[0-9]{1,2})$

If '{min,max}' syntax doesn't work - you could expand like:

    ^(\d+|\d+\.(\d|\d\d))$

    ^([0-9]+|[0-9]+\.([0-9]|[0-9][0-9]))$

Hope that helps.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

JonathonG

try this:

validation-regex="^\d+\.\d{0,2}$"

Jonathon
Independent Interwoven Contractor

Migrateduser

You might want to make the decimal point optional, I think something like:

^\d+\.\d{0,2}$ => ^\d+(\.\d{1,2})?$

dlukezic

Actually, I was looking for something to make the decimal optional, but this is giving me an error on my DCT. The error is: "Either required fields have not been filled out or fields contain invalid values. Please fix this before saving."

Any other suggestions?

Thanks!
Doreen

lhdavis

I seem to recall there being a bug that if you put a validation-regex on a field it is interpreted as a required field. Even if you do not have required="t". Can anyone confirm?

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

dlukezic

I have no idea, but I have not made the field in question of my DCT required.

Doreen

Migrateduser

I've never noticed that one - may only affect a very specific version.

iwovGraduate

..... but this is giving me an error on my DCT .....

Which of the several expressions suggested in earlier posts you are using ? What value did you enter in the field ?

Some useful tools:
Regex Remapper
Regex Validator

dlukezic

If I use: ^\d+\.\d{0,2}$, then entering anything other than something like 123.04 (number, decimal, number) will produce an error. I need to be able to have both the number parts and the decimal optional.

If I use: ^([0-9]+|[0-9]+\.[0-9]{1,2})$, then I can enter a number with no decimal, I can enter a number like 123.04, but I cannot enter .04 alone.

If I use: ^(\d+|\d+\.(\d|\d\d))$, I can only have one decimal point and I have the same issues as ^([0-9]+|[0-9]+\.[0-9]{1,2})$.

And finally, if I use ^([0-9]+|[0-9]+\.([0-9]|[0-9][0-9]))$, it is the same as ^(\d+|\d+\.(\d|\d\d))$.

I have verified all of these with the Regex Validator that you sent me. I don't know how to use the Regex Remapper though.

Any help would be great appreciated!

Thanks,
Doreen

Migrateduser

Ahah, the first part is optional too, but one or the other is required. I think maybe something more like:

^\d+\.\d{1,2}|\d+|\.\d{1,2}$

But let me also say, one way that may be better is to use

validation-regex="price"

Then have FormAPI that checks for tokens like these and replaces them with the corresponding regex when the form loads and when a replicant instance is added. That way, if you want to change your price regex you do it in one place (your FormAPI library) instead of every DCT, and the DCT code is easier to follow. It takes some infrastructure work up front but I've been much happier with this approach in the long run.

Edited by john on 07/14/04 11:41 AM (server time).

BIRT Exampler.jpg

iwovGraduate

Instead of ^([0-9]+|[0-9]+\.[0-9]{1,2})$ , try ^([0-9]+|[0-9]+\.[0-9]{1,2}|\.[0-9]{1,2})$

dlukezic

This is perfect!!!

Thanks very much!
Doreen Smiley Happy