I want to check if anyone is faced with this case I will present and if anyone has any recommendations or suggestions. The case is when you have a pair of fields, lookup list items that are somewhat related in that the value of one is associated with the value of the other. For example, Project and Sub-Project; LOB and Sub-LOB; Root Cause and Sub-Root Cause; Status and Sub-Status etc. As you might know lookup list in ALM projects are static. You can build a multi-level/nested lookup list and use that in the sub-field. But how do you control the main field such that users will only select the top-most level? Right now what we do is the lookup lists for the main field and sub-field are separate list. The lookup list on the main field is one-level so we can be sure that the user can only choose the main LOB for instance. Whereas the Sub-LOB field contains a nested lookup list. This implementation takes a lot of maintenance overhead plus sometimes users will choose a high-level value on the Sub-field that will have to be adjusted. Has anyone thought of a way to make this more systematic? Is there any clever way to get around to it?
↧