Does anyone have any experience of dealing with look ups in the webclient metadata pane that are a little on the heavy side? We have a client that has a list of values in the 10's of thousands that they want to be a look up in the web client (it's already a look up in their forms processes) and whilst it is easy enough to create this as a field, it appears to be causing the web page to become unresponsive when they are selecting more than a few of the files in preparation to start bulk editing.
Question
Question
Replies
Hi Chris,
What version of the Web Client is the customer using?
The HTML element used for drop downs can cause the browser to hang if too many values are returned at once. This is probably what's happening to the customer.
I recommend using the [Settings]MaxDropDownLength attribute. MaxDropDownLength sets an upper limit on the number of values displayed in the drop down. If the lookup exceed this limit, the user must type to filter until the number of values returned is less than the limit. The attribute can be set to any positive integer.
Another useful attribute is the [Settings]CacheFieldValues. When CacheFieldValues is true, the values for the lookup are cached in browser local storage after they first time they're retrieved, offering a slight performance boost. [Settings]CacheFieldValues accepts Booleans (True/False or Yes/No).
Is there any chance of splitting those items up into categories and using dynamic fields? Even if the top level dropdown is something like A-E, F-J, etc...you might be able to speed up the initial load.