You are viewing limited content. For full access, please sign in.

Question

Question

Why Do Scanning and Client Work Differently When Typing a Value in Dynamic Field?

asked on January 15, 2019 Show version history

When working with dynamic fields between LF Scanning and the Windows Client, they behave differently. We have a Dynamic field that is used to populate 4 other fields after a value is selected. The initial dynamic field is populated from a database table of around 40,000 results.

In LF Scanning if you select a Dynamic Field and start typing the value you want, after each number it selects the first value from the list that matches the so far typed in value and then performs the lookup to populate the remaining 4 fields. It does this for each character. For example, we type in Employee ID 123456789. It will find the first value that matches with a 1 and populate the other fields. Then it will find the next value that matches with a 12 and populates the other fields, etc.

In the Windows Client it does not seem to perform the lookup until it selects the final value matching what was typed.

Is there a reason for this discrepancy? Using Windows Client 10.3.1.502 and LF Scanning 10.3.1.306.

1 0

Replies

replied on June 4, 2019

Was this ever figured out? I'm encountering this as well.

0 0
replied on August 1, 2022

Have you had a resolution to this issue?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.