cell security with TM1User()

[Tilo]

Hello Forum,

in the past (10.2.0) we used cell security where the cell security values were calculated with TM1User().
At runtime this means that a cell of the cell security cube would contain a WRITE for certain users and the same cell for other users would contain nothing.
This worked very well without the slightest problems in Tm1 10.2.
In TM1 10.2.2 FP3 this does not work anymore.

My case for a test user:
- For all Groups the user is a member of: The cube security is set to WRITE.
- For all Groups the user is a member of: The Dimension security for all dimensions in the cube is set to READ.
- For all Groups the user is a member of: There is element security for some dimensions and for some dimensions there is not.
At least with one Group the user has READ or WRITE access to the elements of each Dimension with element security he should have Access to.
- For all Groups the user is a member of: The element security for the element 'PLAN' (Dimension "Version") is set to READ.

To be able to Switch on and off the allowance to enter values we use a Special Group Planning and implemented a cell security cube rule:
['PLAN'] = S: IF(DB('}ElementSecurity_cost_center', !cost_center, !}Groups) @= 'WRITE'
& DB('}ClientGroups', TM1User(), 'Planning') @= 'Planning',
'WRITE', STET);

The outcome is that the user has WRITE values in all cells that he should have access to that means all cost Centers he has WRITE Access to and the Version 'PLAN'.

But when accessing the cube to enter data he has WRITE access to only some of the cells and READ Access to all the rest.
The cells he has WRITE Access to can be separated clearly from the cells he has READ Access to - the access is Over all dimensions the same but is different only for members of one Dimension.
This Dimension does not even have element security.

Is this a bug or Have we just been lucky that it worked in TM1 10.2?

Thanks
Tilo

[Tilo]

The cause was a stupid mistake in a rules definition...
Everything seems to works fine now.