Field Constraints

Has anyone noticed that simple field constraints that used to work have stopped? If so, have you found a new format that DOES work? I noticed this in particular as I am working with the new Env 29.2 and CU 25 for Landmark/GHR, but went back and tested in Env 18 and CU 12 and they are not working there either. Below is an example of one that is no longer working:

constraint (PostalAddress.PostalCode entered
and HROrganization = "Community Medical Centers"
or HROrganization != "Community Medical Centers")

I was able to hire someone without a zip code, actually without an address at all!

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Accepted answers

All comments

cockrell

@awells - on first glance, it looks like the value that you are using is the HROrganization.Description rather than the HROrganization code. Can you try updating the constraint to use your HR Organization code, if "Community Medical Centers" is not it, and see if that will work?

apiazza

Hi Shanell! You beat me to the answer! Despite not having changed fields, and where the text description used to work, it does now require the numeric. Change "Community Medical Centers" to 1 and voila a working constraint!

cockrell

Great! So glad that worked and was an easy fix! Wishing you health and safety!

Copyright © 2025 Infor. All rights reserved.