Max number of values in a Values List
I have a field (Functional Area) on my Business Process application that is a values list field, that currently has 115 values. Some of our business users want to add another 50 values to the list. When should I tell them enough is enough and we should create an ODA to create a cross reference for this field instead? What is the recommended Best Practice?
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
- Values List
The Sizing and Performance Guide doesn't specifically call out a limit to the number of values in a single values list. That said, smaller is always better but business is business and sometimes you have to create big lists.
Additionally, and I'm sure this has crossed your mind, it will be easier to maintain and use if you can implement DDEs to filter lists and sub-lists for relevant items. Especially if you're using a custom sort order.
From an end-user performance perspective; if the application has a lot of fields to begin with and a good amount of values list (with a lot of values and they aren't configured as drop-down) the time to load a record (edit/new) will increase as well with the newly added values.
To me an ODA is a little bit of an overkill to just store one piece of text with no other meta data.
I'd let the business users know by having these many values will possibly have a performance impact on the application when adding a new record or updating existing ones.