Hi all,
Here is a new issue I am facing in my quest to integrate TM1 and Cognos BI.
Environment:
Cognos BI 10.1.1
TM1 9.5.2
TM1 cubes are used as data sources in Cognos BI.
Description of the issue:
To improve performance and memory usage, the dimension order of a cube have been changed via the Cube Optimizer wizard.
We did observe a performance improvement, however, in contradiction to what the IBM documentation claims, the dimension order in the BI front end (i.e. Analysis Studio) did change and as consequence doesn’t meet the users requirements.
Is this a normal behaviour? Is there a work around this?
Thanks a lot.
TM1 Internal dimension order and Cognos BI
-
- MVP
- Posts: 3702
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: TM1 Internal dimension order and Cognos BI
If the dimension order changed in analysis studio after performing cube optimization then this is a clear bug and you should raise a defect with IBM.
-
- Posts: 10
- Joined: Fri Jan 11, 2013 4:48 am
- OLAP Product: TM1, Transformer
- Version: TM1 9.5
- Excel Version: 2007
Re: TM1 Internal dimension order and Cognos BI
The order has changed surprisingly. An IBM SR will be raised.
Thanks
Thanks
-
- Posts: 10
- Joined: Fri Jan 11, 2013 4:48 am
- OLAP Product: TM1, Transformer
- Version: TM1 9.5
- Excel Version: 2007
Re: TM1 Internal dimension order and Cognos BI
By the way, IBM came back to me claiming that this was the intended design. Disappointing.