I am wondering if this is working as expected or whether this is a bug.
When working with Multi or Single Dropdown fields and selecting the Data Source as ‘Assets’...
…All Users, Requesters, Agents, Departments but not Locations...
...when a user attempts to use these Dropdown fields in a form from within the Support or Agent Portals they instead work as a Search box:
Why is this the case for everything except Locations? Is there a way to force it to work as a Dropdown instead of a Search box?
Best answer by MDavies
I raised an idea based on this here:
+14I am wondering if this is working as expected or whether this is a bug.
When working with Multi or Single Dropdown fields and selecting the Data Source as ‘Assets’...
…All Users, Requesters, Agents, Departments but not Locations...
...when a user attempts to use these Dropdown fields in a form from within the Support or Agent Portals they instead work as a Search box:
Why is this the case for everything except Locations? Is there a way to force it to work as a Dropdown instead of a Search box?
What I have seen it’s based on the amount of data in the list.
Never checked what the max number of items in the dropdown.
+14
I was wondering this as well. I first noticed this when testing it with Assets and filtering only on Services. At the time of testing there were only two Services in the Inventory which, to me, seems like a low number to force the use of a Search Box instead of a Dropdown List. Our list of Locations is 43-long yet is not forced to act as a Search Box. Very odd...
+14I was wondering this as well. I first noticed this when testing it with Assets and filtering only on Services. At the time of testing there were only two Services in the Inventory which, to me, seems like a low number to force the use of a Search Box instead of a Dropdown List.
Could be source type as well. I just seen it with normal drop downs.
+8Hello
I raised an idea based on this here:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
