Dear All,
Just a question of taste/performance/standards.
I am currently designing a new universe and an interesting thought ‘popped’ my mind. If I have a date, and break I it down into Month, Year and Quarter, should I create the breakdown of the date as objects within a sub-class, or details within the date object?
Would it make a difference either way?
Dave
Listserv Archives (BOB member since 2002-06-25)
<5034A7F3B490D3118A0C00508B092B295282DB@lvl_52_exc_5.lvl.co.uk>, David.Watson@LVL.CO.UK (Watson, David) wrote:
Would it make a difference either way?
Dave,
personally I would create them as objects within a subclass. The reason being is that if they are details as opposed to objects, then this limits what actions can be performed on them when reporting - for example, if you create 2 queries in BO full client, the query results cannot be linked by details but only by objects. Therefore you would not be able to create a single table from the two queries if you had set up the month etc as a detail.
Regards
Brian Patterson
Listserv Archives (BOB member since 2002-06-25)
Good question, as a Designer I was always eager find a user for a Detail Object to give users the full spectrum of colour in their universe, however the limitation of always having to ask for the Object associated with the detail stumped me (not having telephone number in my database, the normally quoted example for a detail).
You will find users will want to create reports based on Date alone, and not always want Month included.
Therefore make it an object.
The only case I’ve found for a detail object is to allow “customised” sorts in Webi.
In some reference tables (Products etc), Users want to see a specific order in Reports. We’ve created “sort order fields”, in the database and created Sort order “detail” objects linked to the associated Product Desc Objects. (To hide this “meaningless” value from view in the report, we’ve change the column object to white text on white background) Hope this helps
Listserv Archives (BOB member since 2002-06-25)
Simon,
I am not sure why you need the sort order objects when BO provides the facility to Custom sort a report, can you please elaborate ??
–
Prasad Shenoy
CMOS Soft Inc., CA
Good question, as a Designer I was always eager find a user for a Detail Object to give users the full spectrum of colour in their universe, however the limitation of always having to ask for the Object associated with the detail stumped me (not having telephone number in my database, the normally quoted example for a detail).
You will find users will want to create reports based on Date alone, and not always want Month included.
Therefore make it an object.
The only case I’ve found for a detail object is to allow “customised” sorts in Webi.
In some reference tables (Products etc), Users want to see a specific order in Reports. We’ve created “sort order fields”, in the database and created Sort order “detail” objects linked to the associated Product Desc Objects. (To hide this “meaningless” value from view in the report, we’ve change the column object to white text on white background) Hope this helps
Free Internet Access from AltaVista: Get it, share it & win! Yahoo Search - Web Search
Listserv Archives (BOB member since 2002-06-25)
At 03:49 PM 1/11/2000 -0800, Presad Shenoy wrote:
I am not sure why you need the sort order objects when BO provides the facility to Custom sort a report, can you please elaborate ??
Simon had said:
The only case I’ve found for a detail object is to allow “customised”
sorts in
Webi.
Presad,
While BO provides Custom sorts, WebI does NOT. Simon was discussing how they’ve allowed customized sorts through detail objects for their WebI users.
Also, there may be times when a customized sort is needed over and over, and all users need the same one. So I can see that having a predefined sort field, even for BusObj full-client users, can be helpful. Each user then does not have to “recreate the wheel” on each and every report.
Regards,
Anita Craig
Stanford University
Listserv Archives (BOB member since 2002-06-25)
Simon_Casdagli@AMP.COM.AU schrieb:
…
The only case I’ve found for a detail object is to allow “customised” sorts in Webi.
…
I can give you another example for the use of “detail objects”: assume you have a database of customers with “customer name” as one of the objects. This is a perfect example of a detail object, because it does NOT make any sense to analyze measures based on a “name” dimension. Normally there will be at least a few customers with the same name who will be collapsed into “one” customer… Especially in Austria or Germany we have lots of Muellers and Muellners in the phone directories… ;-))
Walter
–
Walter Muellner
Delphi Software GmbH / Austria
w.muellner@delphi.at, Tel. +43-1-8151456, http://www.delphi.at
Listserv Archives (BOB member since 2002-06-25)