I am to work on Universe standard document pretty soon. I have a question for you all. Two options:
LOV should be added for all objects??
or
LOV should be removed from all objects(dimensions, measures) and should only be attached to those objects which are specified in requirements.
I think the choice 2 should be a standard…What do you say everyone??
and also could you add up a reason as well with your response…I would guess the unneccessary added processing time??
Very often an LOV for dates is not very useful. If you have few years of history of transactions the LOV with thousands of values is useless. Not to mention if a date contains also a timestamp.
A list of values is supposed to provide value to a user. If you have an object that has a list that is too large, there is no value, thus the reason for leaving LOV settings off for date objects. Measure objects - when used in a query by themselves - will return a single value, which is not very useful. The current version of Designer will automatically turn off the LOV for any measure object.
If something is easy to type (a date value, or even a year value) then there’s not much point in having a list to pick from.