BusinessObjects Board

LOV for all objects

I am to work on Universe standard document pretty soon. I have a question for you all. Two options:

  1. LOV should be added for all objects??
    or
  2. 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??

Thanks a lot in advance!!


yash2008 (BOB member since 2007-12-12)

You’re absolutely right.

LOVs have to be associated only to the needed objects.

This will avoid unnecessary processing time.


Jansi :india: (BOB member since 2008-05-12)

Rule 1: LOV should NOT be used on measures.
Rule 2: If in doubt, refer to rule 1

Yes, that’s right. I failed to notice measures inside parenthesis.


Jansi :india: (BOB member since 2008-05-12)

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.


Marek Chladny :slovakia: (BOB member since 2003-11-27)

This can be a additional rule:

If necessary, make sure to have LOV’s for some Detail objects too.

Ex: Month, Quarter, Year of a date…


pranpad (BOB member since 2008-01-24)

A few more thoughts…

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. :slight_smile: 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.


Dave Rathbun :us: (BOB member since 2002-06-06)