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

[Ashley Snyder1]

Have you looked into extending sys_choice?  As part of the new licensing documentation, it's exempt from the custom tables. You can then use List Collector or even Lookup Select Box (for one value). I know a lot of us developers are running into the same issue and want to continue making things data driven, and even offer users the access to update the data in the tables as they choose without having to edit Select Box variables.

Coming up with a strategy now will save a lot of time down the road and prevent developers from having to go in and edit Select Box values every time a business requirement changes.  

If my response was helpful, please mark as Helpful and consider setting the reply as the Correct Answer if it best answered your question, thank you!