Reporting on a TM1 Cube with Report Studio

[Toto]

Hello,

I am trying to open a TM1-cube in Report Studio after publishing the cube in Framework Manager. When I open the cube I can not see the levels, although I have defined them in }HierarchyProperties and set up a TI-process where I execute the command: RefreshMDXHierarchy('Dimennsion'). Any idea what I may forgot?
Is there something I could have done wrong in }HierarchyProperties? Attached please see my definitions.

Thanks a lot,

Toto

[MarioRubbo]

Did you publish the TM1 cube to C8 after specifying the levels?

[rollo19]

Been having the same issue in Express 9.0

DMR example of what we are expecting (members & levels):

DMR_showing_levels.png (18.74 KiB) Viewed 12569 times

TM1 demo data source (members only):

TM1_showing_members_only.png (18.66 KiB) Viewed 12570 times

Tried editing }HierarchyProperties cube

Used TI to RefreshMDXHierarchy('Products');
Saved & restarted server
Re-published FM package
Same result - no levels.

[rollo19]

hang on a mo - it does work!
I don't think you need to re-start the server either. Just be wary of the C8 refresh lag. I remember there is a parameter somewhere to change that.

[ParisHilton]

hang on a mo - it does work!
I don't think you need to re-start the server either. Just be wary of the C8 refresh lag. I remember there is a parameter somewhere to change that.

I've been suspecting a lag existed , consolidations can take forever to show up in BI. Does anyone know where to find docs on this magic parameter?

[RasMA]

C8 caches the metadata when a package is accessed in the C8 Studios. Sometimes this can introduce a 'lag' in changes to cubes being visible. Try refreshing the rtm package cache.

Cheers,
-MA

[babernat]

I have experienced issues when I specify a specific dimension in the following code:

RefreshMDXHierarchy('Dim Name');

So.... I write is as follows and it works perfectly.

RefreshMDXHierarchy('');

Note: It will refresh for all dimensions.

[merdal]

When making any changes in TM1 model or data, to make sure to see the change in BI front end, and to make sure not to use cache, restart your browser and make sure your browser does not use cached objects from previous browsing sessions.