The Universal GUI used to have a performance problem with ‘Combo’ lookup control so we defaulted to ‘Suggestions’. In the recent GUI’s the performance increased and also the functionality improved so that ‘starts with’ is shown before ‘contains’ in the result. So we are changing most look-ups to ‘Combo’.
So I am wondering, is there still any reason left to use anything else than ‘Combo’ as a lookup control since it has the ‘Suggestions’ functionality included?
+10Hi
is there still any reason left to use anything else than ‘Combo’ as a lookup control since it has the ‘Suggestions’ functionality included?
Yes, there is: when the lookup table contains many records.
Combo still loads the entire lookup set client-side without any $top/paging, as you can see in F12 → Network. So the following from the Thinkwise Performance guide still applies in this case:
"The use of combo boxes for lookup fields is strongly advised against when the lookup table contains many records. This is because the combo box must load the entire dataset to give the user a choice between the items. This worsens the performance and also uses a great deal of the workstation's memory."
Does this help?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
