List Collector vs Select Box

[David Carlin]

Hello,

I have a question I was looking for some input on. I am working on building out catalog items for my company and I have a question about variables. What is the difference between a Select Box vs a List Collector? They both seem to give the same result.

We are running into the issue where some users want a drop down of 40+ options. It seems like this should be a list collector because 40 options is a lot to manually enter. However, a list collector needs a table so we would have to create a custom table with the 40 options.

We also only have so many custom tables as part of our licensing so I don't want to use custom tables on variables for one catalog item.

I am just looking for some input on when is the best time to use a Select Box vs when is the best time to use a List Collector.

Thanks!

David

[Mark Roethof]

Hi there,

Another difference with List Collector and Select Box is, that you could select multiple values with a List Collector.
It's good that you mention an additional table in relation with the licensing. Often this is overlooked, nice that you are carefull with this.

40+ choices sounds a lot. What would the User Experience be? Is it possible to break these choices down (for example like category/subcategory). Also, how are you going to maintain such hugh lists (or is it a static list which almost never will change)?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

[David Carlin]

Hey Mark,

This is for user access to an internal application. As part of the access request, the user must select the role they need and then the group they need to be placed in. The role list contains about 15 roles and the group list contains the 40+ choices. All 40+ groups are available regardless of role.

I feel like this will be a pretty static category since it is access in an application and that does not change much.

[Mark Roethof · Accepted solution]

If both lists are pretty static, and are only used on one specific Catalog Item: I would say just add those choices, not worth thinking about setting up a "choice" table or something similar.

If these choices are also used on other Catalog Items on the Service Portal, or on Form lay-outs in the Platform UI, or these often change, then it would be interesting to think of a more dynamic and maintainable option.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

[rsadhula]

Hi @Mark Roethof ,
What if we want to have multi selection dropdown do we need to use list collection and create custom table ? but this will be a license issue for us