Element not seen by user but only buy admin

Post Reply
AnaRafael
Posts: 1
Joined: Tue Mar 20, 2012 10:38 am
OLAP Product: TM1
Version: 9.5
Excel Version: 2003
Location: Brussels, Belgium

Element not seen by user but only buy admin

Post by AnaRafael »

Hello,

One user has added one element to a certain dimension we are using via a csv file and using a process.
At the end, the user cannot see the element on the dimension.
Myself, as ADMIN, replicated exactly the same steps and it works fine and I can see the element within the dimension.

The interesting part is that this is a recurrent task and we have never faced this issue...

Any idea why this would happen?

Thanks for your help!

Ana
User avatar
jim wood
Site Admin
Posts: 3961
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: PA 2.0.7
Excel Version: Office 365
Location: 37 East 18th Street New York
Contact:

Re: Element not seen by user but only buy admin

Post by jim wood »

While this sounds puzzling I'm not 100% sure it's a bug?
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
declanr
MVP
Posts: 1831
Joined: Mon Dec 05, 2011 11:51 am
OLAP Product: Cognos TM1
Version: PA2.0 and most of the old ones
Excel Version: All of em
Location: Manchester, United Kingdom
Contact:

Re: Element not seen by user but only buy admin

Post by declanr »

... in said TI process does the new element also have its security access created?

I presume your dimension has security on it.

By having access to the TI process any user will be able to run and update the dimension but unless the TI also gives that user access to the element after it is created they will not be able to see it.
Declan Rodger
User avatar
rkaif
Community Contributor
Posts: 328
Joined: Fri Sep 05, 2008 6:58 pm
OLAP Product: IBM Cognos TM1
Version: 9.1 or later
Excel Version: 2003 or later

Re: Element not seen by user but only buy admin

Post by rkaif »

Security might be an issue. Have you checked the security of the new element created?

The other possibility is that the end user may be looking at a static subset and the new element is not part of the Subset. Has the user clicked on the ALL button in the Subset Editor?
Cheers!
Rizwan Kaif
Post Reply