Contributor Approval Hierarchy setting

[LutherPaul]

Hi all,
I am trying to understand the meaning of this alert. I get this while trying to add approval hierarchy dimension for the first time.

When deployed, the currently existing element level security on this subset will be removed.
Do you still want to use this as your current approval subset?


what does this mean? Can someone please explain?

Thanks in advance,
Paul.

[declanr]

The application you are trying to deploy has an approval hierarchy based on a dimension that currently has standard element security applied already.
The apps just use the standard security cubes in the background updated by } (curly bracket) TIs so it needs to overrule the existing security already in place. This stops a user updating an approval node after it has been submitted etc.

[lotsaram]

When using TM1 Application Web the pmpsvc manages element security on the approval hierarchy dimension. If you have created any element security on the dimension used for the approval hierarchy then it will be removed. Simple as that.

It's one of the good things about Contributor and also one of the pains. If you want to reuse dimensions (and cubes) used in the contribution application in other areas of your TM1 model then inevitably you end up duplicating objects in order to be able to control security how you want and not how Contributor wants.

[LutherPaul]

Thanks for the replies with information Lotsaram and Declanr.