Have a question on Dimension Security.
We use an admin module to lock/unlock budget versions (WorkingFcst01, WorkingFcst02, WorkingFcst03, Budet, etc.).
Currently unable to actully unlock WorkingFcst03 so that data can be loaded to the cube even though the dimension element shows as being unlocked. Am able to load to the cube if another version is selected, ie., WorkingFcst01.
Looking for guidance on why WorkingFcst03 would remain locked.
Thank you.
TM1 Security
-
- Posts: 26
- Joined: Sun Mar 10, 2019 9:06 pm
- OLAP Product: TM1
- Version: Planning Analytics 2.0
- Excel Version: Excel version 2013
-
- 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: TM1 Security
Where (in what control cube) are you looking to know that the dimension element is locked ? Which user holds the lock currently? Can that user unlock the element manually?
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
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
- paulsimon
- MVP
- Posts: 808
- Joined: Sat Sep 03, 2011 11:10 pm
- OLAP Product: TM1
- Version: PA 2.0.5
- Excel Version: 2016
- Contact:
Re: TM1 Security
Hi Peter
First check that the element is a base level element and not a consolidation.
Right click on the cell that you are trying to write to and check that no rules apply to the cell
In Perspectives on the View Menu ensure that Display Control Objects is ticked
Expand Cubes and look for }ElementProperties_Version (or Budget_Version, or whatever your dimension is called). Find the element that you are concerned about. If there is no user name against it then it is not locked. If there is and you have Admin rights, you can clear the lock by deleting the user name.
If that is not the problem, then if you don't have Admin Rights then it is possible that someone has changed the security on the element to READ. Find out what Groups your User Id is in by looking at }ClientGroups. Look at }ElementSecurity_<dim> for those Groups and see if at least one of them has more than READ access to the element, ie at least WRITE access.
Check to see whether someone has Reserved the element.
Check to see whether one of the Groups that you are in has at least WRITE access to the cube in which you are trying to write data.
Check that no one has locked the whole cube.
Check that no one has reserved the whole cube.
Check that you have at least WRITE access to all the elements in the other dimensions in the cube.
Check that there is no }CellSecurity_<cube> that is preventing entry
TM1 Security is very flexible. Unfortunately that can mean it can be difficult to work out why a user cannot write to a cell in a cube. We use a utility to automate the above investigations somewhat easier.
Regards
Paul Simon
First check that the element is a base level element and not a consolidation.
Right click on the cell that you are trying to write to and check that no rules apply to the cell
In Perspectives on the View Menu ensure that Display Control Objects is ticked
Expand Cubes and look for }ElementProperties_Version (or Budget_Version, or whatever your dimension is called). Find the element that you are concerned about. If there is no user name against it then it is not locked. If there is and you have Admin rights, you can clear the lock by deleting the user name.
If that is not the problem, then if you don't have Admin Rights then it is possible that someone has changed the security on the element to READ. Find out what Groups your User Id is in by looking at }ClientGroups. Look at }ElementSecurity_<dim> for those Groups and see if at least one of them has more than READ access to the element, ie at least WRITE access.
Check to see whether someone has Reserved the element.
Check to see whether one of the Groups that you are in has at least WRITE access to the cube in which you are trying to write data.
Check that no one has locked the whole cube.
Check that no one has reserved the whole cube.
Check that you have at least WRITE access to all the elements in the other dimensions in the cube.
Check that there is no }CellSecurity_<cube> that is preventing entry
TM1 Security is very flexible. Unfortunately that can mean it can be difficult to work out why a user cannot write to a cell in a cube. We use a utility to automate the above investigations somewhat easier.
Regards
Paul Simon
-
- 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: TM1 Security
See also this topic:
https://www.tm1forum.com/viewtopic.php? ... 919#p71919
https://www.tm1forum.com/viewtopic.php? ... 919#p71919
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
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
-
- Posts: 26
- Joined: Sun Mar 10, 2019 9:06 pm
- OLAP Product: TM1
- Version: Planning Analytics 2.0
- Excel Version: Excel version 2013
Re: TM1 Security
Thank you for the responses.