}ElementSecurity_: do not use it as prefix in a cube

Post Reply
Wim Gielis
MVP
Posts: 3118
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:

}ElementSecurity_: do not use it as prefix in a cube

Post by Wim Gielis »

While I was working on a script for the topic security by user (viewtopic.php?f=3&t=15582), I created a new control cube as:

vCube = '}ElementSecurity_' | Dim | '_2';

Basically, a suffix _2 to the normal security cube for elements on the dimension "Dim".

TI allows you to create such a cube, but writing leads to errors. Even non-sensical errors, such as: "Cell type is consolidated"

Code: Select all

vCube = '}ElementSecurity_TEST';

CubeCreate( vCube, 'test_dim', '}Clients' );

CellPutS( 'HELLO WORLD', vCube, 'A', 'B' );
The above leads to this error message. To test it, add a couple of test values or recreate the situation.
Even if the dimension "TEST" does not exist, this leads to an error.

1 character of a difference and it gives no error and does what it is supposed to do:

Code: Select all

vCube = '}ElementSecurityTEST';
I remove the underscore here.

So the takeaways:
- the error message makes no sense at all
- we should never create cubes starting with "}ElementSecurity_", choose a different name. Probably IBM treats cube names with this prefix in a different way / have their own plans with them.
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
User avatar
scrumthing
Posts: 81
Joined: Tue Jan 26, 2016 4:18 pm
OLAP Product: TM1
Version: 11.x
Excel Version: MS365

Re: }ElementSecurity_: do not use it as prefix in a cube

Post by scrumthing »

Thanks for the information Wim! Didn't know that. Fascinating. :-)
There is no OLAP database besides TM1!
Post Reply