TM1 Forum

Am I just having a senior moment, or are there no intrinsic TI functions to assign security permissions to cubes and dimensions? (Other than doing a CellPutS to punch the permissions straight into }CubeSecurity or }DimensionSecurity cubes, obviously.)

For Element level security you've got ElementSecurityGet / ElementSecurityPut, but unless it's in an obscure part of the help file (not that I'd discount that...) I can't see any comparable functions for cubes and dimensions.

Seniors moment or not you are still correct (if you have another moment just have to remember that you can't CellPutS 'NONE' to a security cube, it has to be a blank string).

The same goes for cube locking/reserving (write to CubeProperties) dimension locking/reserving (write to DimensionProperties) and element locking/reserving (write to ElementProperties_<dimension>. Except that this last one is a conundrum as you can only lock an element this way not unlock it as once the element is locked this also applies to the ElementProperties cube in question. Releasing the lock can only be manual or via API call.)

Has there been a fix for this in tm10 or is it still a manual unlock?

Darkhorse wrote:Has there been a fix for this in tm10 or is it still a manual unlock?

Depends what you mean by "manual". These functionality gaps still haven't been addressed (explicitly) if that's what you mean, but you can still get around it with CellPutS to the relevant cube in question (making sure it exists first and if need be create it on the fly).
Doesn't have to be manual though, this can all be automated with TI.

Also as you have dredged up an old post it gives an opportunity to correct what I stated about element locking which isn't correct as you can get around this in TI by using the CubeLockOverride function. It isn't really very well documented or even at all but by setting this function to true actually allows override to all LOCK level security and not just cube locking.

wow thanks,

I dredged this up because i was using the search function as im having an issue where I want to lock closed elements but when i re run the TI i want to unlock them all first run some tests then relock the ones that fail the test. but I got through my loop the first time perfectly (as nothing was locked) but when i tried to unlock it failed misrably, I will look into this cube overide, if this overrides everything could i override the username in the lock function and return it to empty ?

Darkhorse wrote:... if this overrides everything could i override the username in the lock function and return it to empty ?

Yes.

Thanks all worked a treat