Question

Employee Property Fields

  • 24 October 2023
  • 2 replies
  • 118 views
WyrDavidB
Rank
Userlevel 3
Badge +7

Hi All - I’ve searched in the community and can’t find any similar issues - so raising as a question myself.

We are using employee property fields and have found that the “free fields and properties” screen tries to validate the property value against an LOV regardless of the free field definition. When we try and add the property field in the “employee file” properties section, the system does not try to validate against the LOV.

This shows the property field set up - there is no validation against any LOV

 This is the error when entering on the “free fields and properties” screen

(If an LOV validation is applied, the “free field description” mandatory field is NOT mandatory)

and this is the employee file screen successfully entering similar data

when the overview screen is refreshed, the value saved from the employee file screen can be seen.

 

If any one can advise if they are seeing similar behaviour and whether this is working as designed or there is something else going on, that would be great.
many thanks in advance

Dave

2 replies

vickyrohilya
Rank
Userlevel 2
Badge +6

Hi,

Free Field Description is not mandatory to enter in ‘Free Field and Properties’ screen.

Even you use Property Code with LOV or without LOV, it works fine.

When LOV is enabled, select the available values in ‘Value’ field.

If LOV is not enabled, you can enter any value and save it.

 

Thanks

Vikas Jain

Vikas Jain
WyrDavidB
Rank
Userlevel 3
Badge +7

Hi @vickyrohilya, thank you for your reply.

We know that the free field description is not mandatory in the “free field and properties” screen - even though it is marked as pink/red.

our problem is that on the “free field and properties” screen, regardless of whether we have LOV enabled or not, the screen/system tries to validate the “value” field.

using the addmeddet property field in the example above (which has no LOV validation - first screen shot), when you enter a value and hit save, the system runs this SQL - looking for a LOV where there is none defined.

 

 

{? = call Login_SYS.Init_Odp_Session_(?,?,?,?,?,?,?,?,?,?,?,?)} {? = call Login_SYS.Init_Odp_Session_(?,?,?,?,?,?,?,?,?,?,?,?)} SELECT * FROM (SELECT A.* FROM (SELECT 'W/"'||objid||':'||objversion||'"' etag, 'PropertyValue' luname, 'PROPERTY_CODE='||PROPERTY_CODE||'^PROPERTY_VALUE='||PROPERTY_VALUE||'^' keyref, property_code property_code, property_value property_value, description description FROM PROPERTY_VALUE) A) WHERE (((property_code = 'ADDMEDDET') AND ((property_code = 'ADDMEDDET') AND (property_value LIKE 'none' || '%')))) FETCH FIRST 101 ROWS ONLY {? = call Login_SYS.Init_Odp_Session_(?,?,?,?,?,?,?,?,?,?,?,?)}

 

entering values for the same property on the employee file screen doesn’t trigger the validation for this field.

I think this may be a bug in the  Human Capital Management\HCM Services\Employee Management\Employment\Employee Additional Information\Free Fields and Properties screen but wanted to see if others were seeing the same issue.

Cheers

Dave

 

Reply


Terms & ConditionsCookie settings