LPL Constraint using RegEx

I am trying to place a constraint on a payrate field with four decimal places but it's not working and not sure why...getting an invalid format.

LPL CODE:

PayRate

constraint(PayRate matches "d[0-9][,].d{0,4}|[0-9]d*$")

"InvalidFormat"

label is "NewPayRate

RESULTS:

Find more posts tagged with

LSF/Landmark Development

Accepted answers

All comments

cleverly

The PayRate field in GHR is defined as Decimal size 18.6.

Are you wanting to ensure that that there are only 4 decimals entered, but not 5 or 6? (I can help better if I understand your intent. :-)

patrick-domond

Michael, thank you for now. The issue is something else which I'm looking into and not the Regex.

0909090854053232.pdf

cleverly

There is definitely something a bit wonky going on...

The left hand side of the | in your regular expression would require Landmark to format PayRate with a comma followed by a literal period (which it won't ever do). So it'll never match.

However, the constraint should still evaluate as true because the right hand side of the | should match as long as the input ends with one or more numeric digits, which it clearly does.

We can verify this from a Linux or OS/X command line:

echo 123,456.2300 | egrep --only-matching 'd[0-9][,].d{0,4}|[0-9]d*$'
2300

Now I'm curious to try and fiddle around in Config Console and try and figure out why Landmark evaluates that Regular Expression as false and what modification it would take to coax it into returning true...

Brandon Balkenhol

The matches keyword expects a full match. When I've seen this used in delivered code, Infor begins each RegEx string with ^ and ends it with $. In my testing, I wasn't able to get it to match without including both those characters.

If you want to look at one without searching the whole SpecRepository, check out the Type Field ValidateBankAccountNumber in HCM via LPL Viewer - lines 116 and 147 - for version 2024.07.01..76.

Copyright © 2025 Infor. All rights reserved.