TM1 Forum

I'm running into a problem where some users can't see all named levels on a TM1 datasource in Report Studio. It looks like some kind of caching problem.
The named levels have been defined in the }HierarchyProperties cube. A package has been created using a TM1 cube as a datasource. When I connect to this package from Report Studio I can see all named levels. This is also true (so far...) for all users connecting to this package for the first time. But users that already were working on reports using this package only see the named levels that were available when they first time connected to it - all named levels that have been added later on are not visible/available (even when they log out/in and create a new report). When I save a report using the named levels and one of the 'problem users' opens this report, this user will receive an error message stating that the named level could not be found (reference error).

Has any one else experienced this and found a solution for this issue?

TIA, Michel

Try running the following via Turbo Integrator in TM1

mce wrote:Try running the following via Turbo Integrator in TM1

Code: Select all

RefreshMDXHierarchy('');

I did not mention this in my initial post, but I did run the RefreshMDXHierarchy code on all relevant dimensions. As said, I can see the named levels, as do all users connecting for the first time, but users who connected before still see the old situation.

We just tested with one of the 'problem users' connecting to a new created package and in this package the user sees the named levels. So it looks like that a package re-publish is required to get the named levels available to all users...

Michel

Michel Zijlema wrote: It looks like some kind of caching problem.

did you try restarting TM1 server? if not helped, restarting BI server?

mce wrote:

Michel Zijlema wrote: It looks like some kind of caching problem.

did you try restarting TM1 server? if not helped, restarting BI server?

Recreating the package seems to help. This is not the solution I'm looking for, but I think bouncing either server would be an even worse solution (with regards to availability). Apart from this, in the regarding environment I'm not authorized to bounce servers...

Michel

I know this is old... but I found that if you run your dimensions' TI update processes that were missing the level hierarchyproperties info, followed immediately by a TI process to call RefreshMdxHierarchy(''), you don't have to restart the server.
I'm on 10.1.1

Hopefully this helps someone