Search found 5 matches
- Wed Jul 03, 2013 8:59 pm
- Forum: IBM TM1, Planning Analytics, PAx and PAW
- Topic: Implementing accumulation D-link functionality in TM1
- Replies: 7
- Views: 8539
Re: Implementing accumulation D-link functionality in TM1
You can now achieve this WITHOUT an item dimension in the summary cube. Performance Modeler will let you do this. It creates a few control cubes in the background (behind even control objects) to achieve this. Very useful stuff. I have attached couple of screenshots showing this functionality. D-Lin...
- Wed Jul 03, 2013 8:51 pm
- Forum: IBM TM1, Planning Analytics, PAx and PAW
- Topic: Using picklist/virtual dimension in intercube rule....
- Replies: 5
- Views: 6052
Re: Using picklist/virtual dimension in intercube rule....
You can use an accumulation link in Performance Modeller. Very handy, as before it was hard to accumulate on the Item Dimension.
- Tue Jun 25, 2013 2:12 pm
- Forum: IBM TM1, Planning Analytics, PAx and PAW
- Topic: Cognos BI or Microstrategy over TM1
- Replies: 8
- Views: 8245
Re: Cognos BI or Microstrategy over TM1
Microstrategy is a bit inflexible over TM1, and I found it uses the old OLEDB provider. Nothing particular innovative there. I would def recommend Cognos BI. I would only use MS if is already in place where you are implementing TM1.
- Sun Aug 12, 2012 10:43 am
- Forum: IBM TM1, Planning Analytics, PAx and PAW
- Topic: Anyone using Microstrategy on top of TM1?
- Replies: 2
- Views: 3048
Re: Anyone using Microstrategy on top of TM1?
I have implemented this architecture. Client had already invested in Microstrategy, and we're sold on tm1 adapatablity. The two products don't play well together, despite what Microstrategy will have you believe. It connects via a layer on top of the antequated Oledb provider. Also, the clients repo...
- Wed Feb 22, 2012 5:26 am
- Forum: IBM TM1, Planning Analytics, PAx and PAW
- Topic: Error number 254 and broken TI processes
- Replies: 8
- Views: 11601
Re: Error number 254 and broken TI processes
You should check the }CubeProperties cube and check the DATARESERVATIONMODE property. This can be set to REQUIREDSHARED when you have an active Contributor Application within your model. The TI process needs to aquire data reservation before editing values. Setting the property to OFF will stop this...