Reference field shows "Loading more results"

[Simon Austin]

Hi all,

I have a Reference field field (using an Advanced 'javascript' qualifier) that, when you drop down to view the options, loads 20 results and then proceeds to display "Loading more results..." as you scroll through the list after every 20 entries.

From a User perspective, this is reasonably annoying - every 'load' takes a split second, so the scrolling experience is 'less than smooth'.

I've looked at "Maximum number of items to show for a dynamic drop-down choice list:" in System Properties > System (which I believe maps to 'glide.xmlhttp.max_choices'), however this is set to '15' and therefore likely not the culprit.

Is there any way I can increase this limit for this particular field, or otherwise alter the behaviour of the drop down to encourage it to pre-populate more of the available choices (I'd like it to be exhaustive, ideally) ?

Thanks in advance for your time and assistance,

Simon

[Steven G_]

Hi Simon,

I am trying to envision what the challenge is, could you post some screen shots of the items for everyone to understand better?

[Simon Austin]

Sure thing - hopefully this helps to describe what I'm seeing:

1. When you first click on the dropdown for the field, you get a 'Searching...' message:

2. Subsequent to that, as you scroll, you get a 'Loading more results...' message:

As I mentioned above, the 'loading' action takes a short amount of time, which makes the scrolling process very disjointed; it also means that the 'scroll progress indicator' on the right-hand side inaccurately reflects the 'number of choices remaining' which further confuses the matter.

Would appreciate any ideas you have, and thanks again,

Simon

[Steven G_]

Hi Simon,

Can you post the dictionary record for this field? I am interested in looking to see if there is any refrence qualifier for this list.

[Simon Austin]

Thanks again, Steven.

It's actually a Variable, but it is using an Advanced 'javascript' qualifier which is reasonably complicated; that said, I've simplified it to the following and still the behaviour noted above persists:

javascript:'u_active=true';

Any thoughts?

Simon