Hi all,
I have a cube with three dimension - time , area, product.
when the value of time dimension is 2005 ~ 2006 , the sort order of area dimension was like this:
UK, US, JAPAN, KOREA, CANADA
when the value of time dimension is 2007 ~ 2008 , the sort order will be set to:
KOREA, CANADA, UK, US, JAPAN
How could I accomplish this task? Should I reload the data in 2007 ~ 2008? So, I could use the sort-by-input function in TI.
Or, there are some other better ways to achieve this?
Thank you!
Different sort order in one dimension?
Different sort order in one dimension?
Last edited by imnini on Thu Feb 17, 2011 7:18 am, edited 1 time in total.
- jim wood
- Site Admin
- Posts: 3958
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Different sort order in one dimension?
I'm no expert on this but you may want to look at MDX. You can do this via the subset editor or TI,
Jim.
Jim.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Re: Different sort order in one dimension?
I wonder if we could achieve this in Cognos 8.4 report studio.....???
-
- Posts: 35
- Joined: Fri Oct 15, 2010 7:29 pm
- OLAP Product: IBM Cognos TM1
- Version: 9.5+
- Excel Version: 2007 and 2003
- Location: Minneapolis, MN, USA
Re: Different sort order in one dimension?
Turbo Integrator will not allow you to have different sort orders in one dimension. If you attempt to do it, you will receive an error "%s: sorting information mismatch for this dimension". This is actually an issue I am currently trying to solve right now with my consolidated elements being sorted by input and my leaf level elements sorted by name. The way we are tackling this issue is just going back into the source data and sorting it there, and then sorting everything in turbo Integrator by input. This method works for use because the dimension we are loading is a one time load, so it isn't that big of deal to manually set up the dimension the correct way one time. I would suggest that approach if it is applicable to your situation. Otherwise I would pursue some MDX statements that will accomplish your goal. But my MDX knowledge is rather rudimentary so I would think, but not know for sure, if it is possible/practical.
http://forums.olapforums.com/viewtopic.php?f=3&t=4191
http://forums.olapforums.com/viewtopic.php?f=3&t=4191