Home › Discussions › Questions & Answers › Performance Issue: Slow Load Time for Large LOVs
Customer · · Questions & Answers · 5 replies
We have an LOV tied to a huge table, and when users select the report, the system hangs while it tries to query all possible parameter values in the background. Is there a way to avoid this?
Yes, this performance issue occurs because the default behavior queries all values. You must enable the ‘Filter Before Display’ setting in the LOV definition.
How does ‘Filter Before Display’ solve the loading issue?
When checked, ‘Filter Before Display’ prompts the user to enter a partial value *before* the LOV attempts to display, forcing the form to query only a restricted dataset, thereby avoiding the slow initial load time.
Where is this setting found?
You can modify this setting via Tools > LOVs, where the LOV is defined, or if it is a custom LOV, within the parameter definition itself.
Sign in with LinkedIn or Google to take part.
