Incorrect Display of Hierarchies in BI from TM1

[babernat]

Any help would be greatly appreciated on the following problem:

Please see attached to see the problem I am experiencing.

As a summary, I have established hierarchy properties for a time dimension as follows:

All Periods = Level000
Years = Level001
Quarters = Level002
Month = Level003

In Report Studio when I drill into the hierarchy named Years I see quarters and months appearing at the same level as years.

Thoughts?

BI Hierarchy Display Issue.doc

(47 KiB) Downloaded 395 times

[BigG]

hi, does this help?

Now that the named levels are defined we must create the RefreshMdxHierarchy Turbo Integrator script and then executed it. This script requires a single parameter which informs it of the dimension whose hierarchy must be updated. This however does not affect the method TM1 creates MDX and only allows the named levels to override the defaults set in the hierarchy generation.

When creating the TI script leave the defaults set and click the Advanced then Prolog tab.

Enter RefreshMDXHierarchy(‘dimension name’) where dimension name is the dimension the default member and named levels have been added.

[babernat]

I have attempted rerunning RefreshMDXHierarchy and this hasn't resolved the issue.

Thanks for the response.

[mce]

Default element is not from the top level. This might be confusing Cognos 8. Try putting a default element in Hierarchy Properties file that is in top Level. If you have only one element visible to user in the top level that element becomes the default if you do not specify the top element. If the user does not have access to default element you specified and if you have a single element from the top level accessible by the user, then this top level element becomes the default.

[mce]

If you have alternate hierarchies in your dimension and if element are in different levels for different hierarchies, then you might have this issue. Make sure any element is always in the same level in any alternate hierarchy.

[BigG]

Hi Baberbat, did you resolve this in the end? interested in what the issue was...

[dan.kelleher]

We were experiencing an issue which is kind of related to this:

We have a 'month' dimension as follows:

month.jpg (23.71 KiB) Viewed 5062 times

The issue was that when we set the default member to 2014_04, the MUN that was returned related to the All YTDs hierarchy rather than the All Months hierarchy.

I tried ensuring the indices of the All Months hierarchy came before the All YTDs hierarchy using dimensionsortorder, but this didn't resolve.

It turns out that BI will reference the MUN of the highest level occurence of the element - i.e. choosing 2014_04_YTD over 2014_Q2 because it's higher up in the hierarchy level.

In order to resolve this we simply added another consolidation above All YTDs.

Thought it was worth posting here in case anyone else experiences the same issue.