Hi All,
I have a small question which I am hoping someone has come across.
I have a very large dimension containing cost centres which are organised in a particular hierarchy. Each of the elements is also flagged with a specific attribute which identifies a different purpose for the cost centre. Rather than create another hierarchy to cater for the alternative structure I'd like to use the attribute but I've never aggregate this before and so a little unsure whether it is possible or not. My dimension has about 24000 elements, which are built into an xdi so the maintenance of two large structures is eye-watering.
Your thoughts greatly appreciated.
Thanks
Ajay
Aggregation by Attribute
-
- Posts: 25
- Joined: Sat Nov 07, 2009 5:37 am
- OLAP Product: TM1, CX
- Version: 9.5.2
- Excel Version: 2007
Re: Aggregation by Attribute
Ajay,
I'm sure someone more experienced can give you an "official" answer, but if you're asking if a numeric attribute of a dimension will aggregate by default (say in the }ElementAttributes_dimname cube) then my experience is no.
You could certainly use the attribute in a turbo integrator process to build your alternate hierarchy though and determine the element's parents with the built in TI functions.
I'm sure someone more experienced can give you an "official" answer, but if you're asking if a numeric attribute of a dimension will aggregate by default (say in the }ElementAttributes_dimname cube) then my experience is no.
You could certainly use the attribute in a turbo integrator process to build your alternate hierarchy though and determine the element's parents with the built in TI functions.
-
- MVP
- Posts: 3703
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Aggregation by Attribute
I am a big fan of dimension worksheets but maintaining a dimension of 24,000 elements in an XDI seems crazy, not to mention masochistic. Is there any reason why the dimension is maintained this way except for "is has always been done this way"?
If you migrate this dimension to maintain via TI then building multiple hierarchies based on the attributes won't be a problem.
If you migrate this dimension to maintain via TI then building multiple hierarchies based on the attributes won't be a problem.