Hi Listers,
I am in the midst of development of a new universe. I have entered all the objects I want to use and
now am trying to determine which are dimensions and which are details. My sample Oracle table
“Action Items” looks like the following: #AInumber #Board Name #Board Date
NameAssigned
Organization
Description
It seems obvious that I would define NameAssigned, Organization, and Description as Detail objects,
but related to what dimension? My initial thought is that I create an object called “Action Item”
defined as the concatenation of the primary key fields AInumber, Board Name, and Board Date, then
relate the Detail items to that Dimension. If I do, then I guess I should define these objects as
Details also. I didn’t design the database and I can’t change the design.
Am I heading down the right path?
Thanks in advance,
Roger Poole
rpoole@nswc.navy.mil
I don’t see any problem with concatenating the primary key fields into
one object called ‘Action Item’, but that would not be a detail
object-- it would be a dimension object. ‘NameAssigned’,
‘Organization’, and ‘Description’ would then be detail objects of the
‘Action Item’ dimension.
I would suggest that you also create individual objects for each
column of the primary key (‘AInumber’, ‘Board Name’, and ‘Board Date’)
so that your users can use them as conditions or to sort the data, for
example by date. You could make them detail objects of the ‘Action
Item’ dimension object, but if you do, your users will not be able to
use them for drill down. For that reason, I would suggest making them
dimension objects. You can define hierarchies of dimension objects
using the hierarchy editor.
I am in the midst of development of a new universe. I have entered
all the objects I want to use and
now am trying to determine which are dimensions and which are
details. My sample Oracle table
“Action Items” looks like the following: #AInumber #Board Name #Board Date
NameAssigned
Organization
Description
It seems obvious that I would define NameAssigned, Organization, and
Description as Detail objects,
but related to what dimension? My initial thought is that I create
an object called “Action Item”
defined as the concatenation of the primary key fields AInumber,
Board Name, and Board Date, then
relate the Detail items to that Dimension. If I do, then I guess I
should define these objects as
Details also. I didn’t design the database and I can’t change the
design.
Am I heading down the right path?
Thanks in advance,
Roger Poole