I need to show month names (Jan - Dec) in X-axis and the relevant account values for current Year and Prior Year as lines in a line chart.
I have a period dimension in the TM1 cube which contains Years (2013 and 2014) as 2 different members and underneath these members, we have different months (Jan 2013..Dec 2013 and Jan 2014...Dec 2014) as members. I need to display Jan - Dec in x-axis and the corresponding values for 2013 and 2014 for a particular account going as lines. The problem I have is, I am not able to display Jan - Dec (generically). I was able to show 24 months (Jan 2013 to Dec 2014) in x-axis because of the uniqueness of the month values in the cube. How can I display Jan - Dec generically in X-AXIS?
Thanks.
Quote from: twister on 18 Aug 2014 09:30:58 AM
I need to show month names (Jan - Dec) in X-axis and the relevant account values for current Year and Prior Year as lines in a line chart.
I have a period dimension in the TM1 cube which contains Years (2013 and 2014) as 2 different members and underneath these members, we have different months (Jan 2013..Dec 2013 and Jan 2014...Dec 2014) as members. I need to display Jan - Dec in x-axis and the corresponding values for 2013 and 2014 for a particular account going as lines. The problem I have is, I am not able to display Jan - Dec (generically). I was able to show 24 months (Jan 2013 to Dec 2014) in x-axis because of the uniqueness of the month values in the cube. How can I display Jan - Dec generically in X-AXIS?
Thanks.
Hi,
In a nutshell, the structure of your cube is preventing you from being able to do this. Currently you have months as a level below years in your periods dimension, so you do not have one generic member for (say) January - you have separate members for the months within each year.
To do what you desire, you would need to have a separate Months dimension in your cube, containing 12 month members. Your years would need to be in a different dimension.
Cheers!
MF.
Thanks for the response. Yes. I agree with what you are saying but unfortunately the structure can't be changed at the moment. Could you think of any workaround?
I am trying to come up with a workaround.
Thanks.
Quote from: twister on 18 Aug 2014 10:06:06 AM
Thanks for the response. Yes. I agree with what you are saying but unfortunately the structure can't be changed at the moment. Could you think of any workaround?
I am trying to come up with a workaround.
Thanks.
I had the same requirement with a PowerCube and the only solution I found was to add the generic Months dimension. What is the objection to changing the structure? It seems to me that at least one of the primary reasons for a cube's existence is to support reporting. In fact I'd argue that in some cases the only reason for a cube's existence is to support reporting. Therefore why resist enhancing the structure to support reporting? If you add the month dimension then it shouldn't break any existing reports.
Thanks for the response Lynn. We are having TM1 resource issues at the moment and that is the reason I am trying for a workaround. I am normally optimistic in finding workarounds but I am failing miserably here. I guess the only way is to add an extra dimension to overcome this problem.
Thanks.
Quote from: twister on 18 Aug 2014 10:51:52 AM
Thanks for the response Lynn. We are having TM1 resource issues at the moment and that is the reason I am trying for a workaround. I am normally optimistic in finding workarounds but I am failing miserably here. I guess the only way is to add an extra dimension to overcome this problem.
Thanks.
I don't think you would find a workaround for this, since a dimensional report deals with members not values. If you had a relational source, you could derive the month values and use these, but it just wouldn't work with an OLAP source.
Cheers!
MF.