Element Lock not working
-
- Posts: 2
- Joined: Tue Oct 16, 2012 1:48 pm
- OLAP Product: TM1
- Version: 9.5.2
- Excel Version: 2007
Element Lock not working
Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
Can anybody help me in understanding how to restrict data updation via TI when we lock the element.
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
Can anybody help me in understanding how to restrict data updation via TI when we lock the element.
-
- Regular Participant
- Posts: 424
- Joined: Sat Mar 10, 2012 1:03 pm
- OLAP Product: IBM TM1, Planning Analytics, P
- Version: PAW 2.0.8
- Excel Version: 2019
Re: Element Lock not working
"You Never Fail Until You Stop Trying......"
-
- MVP
- Posts: 3667
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Element Lock not working
Element locking should prohibit data entry by admin users (that includes TI). If is doesn't then that's a bug, what version are you using?radhikah78 wrote:Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
Can anybody help me in understanding how to restrict data updation via TI when we lock the element.
Does the TI process contain the function CubeLockOverride(1) in the prolog?
BariAbdul, I'm really not sure of the relevance of the link you posted.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Regular Participant
- Posts: 424
- Joined: Sat Mar 10, 2012 1:03 pm
- OLAP Product: IBM TM1, Planning Analytics, P
- Version: PAW 2.0.8
- Excel Version: 2019
Re: Element Lock not working
![Embarrassed :oops:](./images/smilies/icon_redface.gif)
"You Never Fail Until You Stop Trying......"
-
- Posts: 2
- Joined: Tue Oct 16, 2012 1:48 pm
- OLAP Product: TM1
- Version: 9.5.2
- Excel Version: 2007
Re: Element Lock not working
Hi,
We are using TM1 10.2.1 version.
The TI's that we have written does not have function CubeLockOverride.
We are using TM1 10.2.1 version.
The TI's that we have written does not have function CubeLockOverride.
-
- MVP
- Posts: 264
- Joined: Mon Nov 03, 2014 8:23 pm
- OLAP Product: TM1
- Version: 9.5.2 10.1 10.2 PA2
- Excel Version: 2016
Re: Element Lock not working
That's exactly correct. Essentially every TI runs as admin regardless of the user who executes it. That's why they need to be created by an admin and why an admin needs to define who has access to see and run the TI process.radhikah78 wrote:Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
http://www-01.ibm.com/support/knowledge ... ml?lang=en
-
- Regular Participant
- Posts: 424
- Joined: Sat Mar 10, 2012 1:03 pm
- OLAP Product: IBM TM1, Planning Analytics, P
- Version: PAW 2.0.8
- Excel Version: 2019
Re: Element Lock not working
Thanks BrianL ,That's exactly what I was trying to say.Post by BrianL » Mon Apr 27, 2015 8:04 pm
radhikah78 wrote:
Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
That's exactly correct. Essentially every TI runs as admin regardless of the user who executes it. That's why they need to be created by an admin and why an admin needs to define who has access to see and run the TI process.
http://www-01.ibm.com/support/knowledge ... ml?lang=en
"You Never Fail Until You Stop Trying......"
- Alan Kirk
- Site Admin
- Posts: 6610
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Element Lock not working
I think it may be an idea to take a look at what Lotsaram was saying again. Yes, the process runs as Admin. BUT when an element is locked, even Admins (which obviously includes TIs) should not be able to write to the cell (unless CubeLockOverride(1) is used). Create an N level view. Now lock one of the elements. You will see that even you, as Admin, will then see the cells in gloriously grey and when you right click on the cell and select Edit Status you will be told that you have no write access to the cell until you UNlock it. If TIs can trample over that, regardless of whether they run as Admin, then something is broked.BrianL wrote:That's exactly correct. Essentially every TI runs as admin regardless of the user who executes it. That's why they need to be created by an admin and why an admin needs to define who has access to see and run the TI process.radhikah78 wrote:Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
http://www-01.ibm.com/support/knowledge ... ml?lang=en
Edit: Just for laughs I checked that this ran as expected in 10.2.2. Sure enough, "Error: Prolog procedure line (5): Element "Monetary" in dimension "RS_Measures" is locked." As one would both expect and hope. Double Edit: I also checked in 9.5.2 which radhikah78 indicates in their profile as their version (which it may or may not be); same result.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
- Alan Kirk
- Site Admin
- Posts: 6610
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Element Lock not working
Except that it gives the wrong impression for this specific set of circumstances, which is a rarity for BrianL and based on his answers to date was almost certainly down to a misreading of the question than a misunderstanding of the principles. The question of whether a TI runs as Admin isn't important if an Admin can't do a particular thing either. It takes only minutes to test that that's the case, and beats relying on interpreting the manuals (which have been known to be wrong, misleading or at least incomplete on occasion as well).BariAbdul wrote:Thanks BrianL ,That's exactly what I was trying to say.Post by BrianL » Mon Apr 27, 2015 8:04 pm
radhikah78 wrote:
Hi,
When we apply element level lock what we have found is it restricts manual input, but if anybody updates data using TI then it allows to update.
That's exactly correct. Essentially every TI runs as admin regardless of the user who executes it. That's why they need to be created by an admin and why an admin needs to define who has access to see and run the TI process.
http://www-01.ibm.com/support/knowledge ... ml?lang=en
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- MVP
- Posts: 1817
- 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 Lock not working
This would be a surprising bug; by any chance when you say "apply element locking" do you actually nean element level security as opposed to cell locking?
Declan Rodger
-
- MVP
- Posts: 3667
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Element Lock not working
I think you might be onto something. It seems that BrianL may have the right answer through a misreading of the OP's question and Alan has already done the experiment to confirm that Element Locking does not seem to be broken in either 9.5.2 or 10.2.2. Only radhikah78 can say if they actually meant Element (read) Security as opposed to Element Locking, (but if that is the case then an apology is probably in order.) There is a good article covering the TM1 security locking concept here.declanr wrote:This would be a surprising bug; by any chance when you say "apply element locking" do you actually mean element level security as opposed to cell locking?
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
- Michel Zijlema
- Site Admin
- Posts: 712
- Joined: Wed May 14, 2008 5:22 am
- OLAP Product: TM1, PALO
- Version: both 2.5 and higher
- Excel Version: 2003-2007-2010
- Location: Netherlands
- Contact:
Re: Element Lock not working
Maybe I've gone through this thread too quickly, but...
Reading the fine manual on element security it states:
Michel
Reading the fine manual on element security it states:
Doesn't this imply that Admin rights count higher than Lock rights and because of this someone (or a TI process running) with Admin rights has the ability to write against an element, even when the element was locked by some user?Locking and Unlocking an Element
When a user locks an element, only those users who have Admin rights for that element can update the data that it identifies. Even the user who locks the element cannot update its data, unless they have Admin rights for that element.
Michel
- Alan Kirk
- Site Admin
- Posts: 6610
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Element Lock not working
The manual does indeed imply that, I concur.Michel Zijlema wrote:Maybe I've gone through this thread too quickly, but...
Reading the fine manual on element security it states:Doesn't this imply that Admin rights count higher than Lock rights and because of this someone (or a TI process running) with Admin rights has the ability to write against an element, even when the element was locked by some user?Locking and Unlocking an Element
When a user locks an element, only those users who have Admin rights for that element can update the data that it identifies. Even the user who locks the element cannot update its data, unless they have Admin rights for that element.
And the manual is a bloody liar. I sense another entry for the "Documentation Deficiencies" thread.
Try it out for yourself. As soon as you lock the element, even though you're an admin, you will see the cells turn grey (when you recalculate anyway) and you will not be able to change that value. Nor will a TI process be able to do it unless you use the function which forces the overrride. Otherwise you get the error message that I cited above.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- MVP
- Posts: 3667
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Element Lock not working
The documentation is well, wrong. What it SHOULD say is only the user owning the lock (OR any member of the Admin group) can release the lock. While a lock is in place no user can update, including Admin. This holds true for all lock types; cube, dimension and element. Again how it actually works is explained here (as opposed to what the documentation might claim, which has never been the way locking has worked.)Michel Zijlema wrote:Maybe I've gone through this thread too quickly, but...
Reading the fine manual on element security it states:Doesn't this imply that Admin rights count higher than Lock rights and because of this someone (or a TI process running) with Admin rights has the ability to write against an element, even when the element was locked by some user?Locking and Unlocking an Element
When a user locks an element, only those users who have Admin rights for that element can update the data that it identifies. Even the user who locks the element cannot update its data, unless they have Admin rights for that element.
As any admin can release a lock it is pretty easy for them to get around the lack of write access but does at least prevent unintended changes by unthinking admins.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
- Michel Zijlema
- Site Admin
- Posts: 712
- Joined: Wed May 14, 2008 5:22 am
- OLAP Product: TM1, PALO
- Version: both 2.5 and higher
- Excel Version: 2003-2007-2010
- Location: Netherlands
- Contact:
Re: Element Lock not working
I think that would be Reserve rights - in case of Lock rights only an admin can undo the lock.lotsaram wrote:What it SHOULD say is only the user owning the lock (OR any member of the Admin group) can release the lock.
Interesting this - based on the documentation I always assumed the Reserve and Lock rights were just another level in an 'hierarchy' of rights, where the 'higher' right will automatically have priority on the lower right. I thought this was also the reason for having a thing like Security Overlays in TM1 Applications: to be able to actually lock a cell for writing, even for an user with Admin rights.
Michel
- Michel Zijlema
- Site Admin
- Posts: 712
- Joined: Wed May 14, 2008 5:22 am
- OLAP Product: TM1, PALO
- Version: both 2.5 and higher
- Excel Version: 2003-2007-2010
- Location: Netherlands
- Contact:
Re: Element Lock not working
LOL BTW - the issue seems to be the application (at least for radhikah78) is behaving as documented ![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)