Unable to Fetch Data

Post Reply
bubidibabadi
Posts: 11
Joined: Tue Jul 23, 2019 7:19 pm
OLAP Product: TM1
Version: 10.2.2, Planning Analytics wit
Excel Version: 2010

Unable to Fetch Data

Post by bubidibabadi »

Hello Guys,

One of the user is unable to access the cube A in workspace. They are getting "unable to fetch data. user does not have read access".

Cube A has 3 security groups related to it, lets say Group A, Group B, Group C.

The user has write access to Group A, but is not assigned to Group B and Group C.

I have checked the dimension security as well and all the dimensions in Cube A have read access to all the Groups. Doesn't this mean she should be able to view the cube?

What could be the possible reason why the user is unable to access?

Thank you.
Regards,
bubidi.
tomok
MVP
Posts: 2831
Joined: Tue Feb 16, 2010 2:39 pm
OLAP Product: TM1, Palo
Version: Beginning of time thru 10.2
Excel Version: 2003-2007-2010-2013
Location: Atlanta, GA
Contact:

Re: Unable to Fetch Data

Post by tomok »

bubidibabadi wrote: Mon Mar 23, 2020 7:27 pm I have checked the dimension security as well and all the dimensions in Cube A have read access to all the Groups. Doesn't this mean she should be able to view the cube?
What about any }ElementSecurity_xxxx cubes, or even }CellSecurity cubes?
Tom O'Kelley - Manager Finance Systems
American Tower
http://www.onlinecourtreservations.com/
Wim Gielis
MVP
Posts: 3105
Joined: Mon Dec 29, 2008 6:26 pm
OLAP Product: TM1, Jedox
Version: PAL 2.0.9.18
Excel Version: Microsoft 365
Location: Brussels, Belgium
Contact:

Re: Unable to Fetch Data

Post by Wim Gielis »

Best regards,

Wim Gielis

IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
bubidibabadi
Posts: 11
Joined: Tue Jul 23, 2019 7:19 pm
OLAP Product: TM1
Version: 10.2.2, Planning Analytics wit
Excel Version: 2010

Re: Unable to Fetch Data

Post by bubidibabadi »

Thanks a lot for the tomok and Wim! Apparently the issue was in cell security. We fixed it.
Regards,
bubidi.
Post Reply