Why is the Name of Employee Field Populating During a Search?

asked on March 15, 2017

We have setup a template with dynamic fields. as follows:

When assigning a template in the LF Client it behaves as expected and does not allow you to choose an employee name from the database, but rather populates after an employee ID and/or an Applicant ID is selected.

When searching however, we are seeing different behavior. When performing a field search and having the Applicant ID, Employee ID, Name of Employee, and Social Security Number fields added, when clicking into the Name of Employee field it performs a database lookup and brings back a list of employee names. It does not do this for any of the other fields.

So my question is why does it do it on the Name of Employee field?

LF Client & Server v.10.1.1.320.

1 0

SELECTED ANSWER

replied on March 15, 2017

Is the "Name of Employee" field of the type, list, rather than text? If so, then that could explain why it's showing values when that field is used in an independent field search. If you change the field type to text and then close and reopen the desktop client, see if that addresses the behavior.

0 0

View 1 previous reply

replied on March 15, 2017

You're welcome.

Dynamic field rules don't apply when the fields are used independently from the template.

0 0

replied on March 15, 2017

Good to know. Thanks again.

0 0

replied on March 15, 2017

No problem. Also, just for further clarification, the issue was that because the "Name of Employee" was a list field being used independently of the template, the values you saw in the search pane are actually the hard coded list values configured in the Administration Console, not the actual values being looked up from the external table.

0 0

Question

Question

Why is the Name of Employee Field Populating During a Search?

Answer

Replies

Sign in to reply to this post.