We try to eliminate some bottlenecks in the application and found out that a lot of resources are used by one suggestion control that looks up data from a big dataset (400.000 rows) based on a view.
I found out that the lookup query is fired after each character that is entered. I believe, in this case, it would be better to execute the query for example 200 milliseconds after the last key is touched.
The lookup is used hundreds of times per day, so the impact is significant when it would work in a different way. Is there maybe a trick or setting for this?
Page 1 / 1
Hello Harm,
Right now configuring the delay between a keystroke and invoking its suggestion query is impossible. However, I think this is an excellent idea, in particular because auto-completion-only lookup fields already work like this, with indeed a 200 ms delay.
This raises a question for me. How does the UI behave if the problematic lookup suggestion control is replaced with an auto-completion control? If this turns out to be an unsatisfactory improvement then I fear that implementing this for suggestion controls will only be a partial solution to the problem.
Kind regards,
Henk
Hi Henk,
Thanks for your response.
I have set the lookup control to “Suggestion” and then to “Suggestion starts with” which works considerably better.
I do not see the 200ms delay that you think should be there, at least not in the Windows GUI.
The problem is mainly in the case of a lookup to a large dataset. In this case it concerns a view with more than 300,000 rows.
Ideally, in the case of lookups to large datasets, you would like to have full control over the way of filtering. An option to base a lookup on a table function would be a great improvement.
I hope that in the future a lookup can also be made to a web service, for example to search for companies in the business register of the Chamber of Commerce.
Furthermore, I hope that in the future more advanced search/filter methods will become available for the combination filter. There too it is often difficult to make large datasets perform well.
Is this something that is already on the roadmap?
Best regards,
Harm
Hello Harm,
Apologies for being unclear, it was the ‘Auto complete’ control I was wondering about, see screenshot below:
User Interface → Subjects → Columns → Look-up (Software Factory)
Suggestion controls have a 100 ms delay, auto completion controls have a 200 ms delay instead, which I think will give a good indication of what such a delay will do for user experience. If this turns out to be positive, I’ll look into extending the 100 ms delay for suggestion controls.
As for the other suggestions, I agree that those are great ideas (table valued functions for example), but to prevent us from going too far off-topic I’ll refer to Roadmap 2025 H1.
