MDX odbo output problem

[shockwave]

Hi Guys,

I have an issue trying to output a complex view where when I would untick "ignore consolidated elements" ( keep condolidated elements) the process would take ages to run ( 15+ minutes to run). I want to load this into a summary cube sending all consolidated numbers into n level elements in the destination cube.

I have a current working solution that uses the ODBO datasouce tab in the ti process utilising and mdx statement to output the result. The process takes 30seconds as opposed to 15+ minutes. However, the output is not exactly what i expected to see, but with a bit of logic i was able to get around it. When I initially created the view I was using an application called: MDX Sample application to get the desired view. When i viewed the output i was happy with it but when I created it in my ti process it was a little difference ( see screenshot a ( MDX Sample application) v scrrenshot b ( tm1 TI process)

screenshot a)

mdx sample app output

mdxSampleApplicationMDXoutput.png (36.65 KiB) Viewed 2443 times

screenshot b)

TM1_MDXoutput.png (52.13 KiB) Viewed 2443 times

The output i expected was just one column ( as per screenshot a) per stacked dimension per my query but it has returned the expected result + in v2 but also has pulled back the parent as well. The same has happened with my product returning it at v7 but then returning the parent back up the tree to v4...

Is there something that I am missing from my statment that is pulling back these columns OR is this just the way it is??

Cheers

Shock

[shockwave]

Hi Guys,

was able to come up with a more reliable way by creating a view loading the souce cube and then destroying the view, but still confused to why when running the mdx query within TI it gives me multiple columns as opposed to what it looks like in screenshot a... Can anyone shed some light on why this is?

Cheers

Shock