Page 1 of 1
Unable to write to two WRITE members on control dim
Posted: Tue Aug 29, 2017 5:49 am
by vladino
Hi guys,
we are experiencing a bit weird behavior on our TM1 application with control dim.
We have an application with Version dim as a control dim. Two members are set to WRITE but users are able to write only to the second one in the list. The first remain in read-only mode even if the group has WRITE access for both elements in Element security cube.
Or is this standard behavior of control dim?
BR
Vladino
Re: Unable to write to two WRITE members on control dim
Posted: Wed Aug 30, 2017 11:07 am
by qml
When you say your version dim is a 'control' dim do you simply mean its name is prefixed with the '}' character or do you mean it's actually one of TM1's pre-existing control dimensions?
How is this dimension updated? I would assume it's updated via TI? Are you by any chance using DIrect functions to do that?
Is your Element security done via rules?
Are there any other object security types used e.g. Cell Security?
Re: Unable to write to two WRITE members on control dim
Posted: Wed Aug 30, 2017 8:27 pm
by vladino
Hi,
ok, it seems I haven't explained the situation very well...
qml wrote: ↑Wed Aug 30, 2017 11:07 am
When you say your version dim is a 'control' dim do you simply mean its name is prefixed with the '}' character or do you mean it's actually one of TM1's pre-existing control dimensions?
By "control dimension" I mean this:
https://www.ibm.com/support/knowledgece ... nsion.html
qml wrote: ↑Wed Aug 30, 2017 11:07 am
How is this dimension updated? I would assume it's updated via TI? Are you by any chance using DIrect functions to do that?
It's updated manually.
qml wrote: ↑Wed Aug 30, 2017 11:07 am
Is your Element security done via rules?
Partially yes - CTRL group has WRITE access to all versions, other groups are maintained manually.
qml wrote: ↑Wed Aug 30, 2017 11:07 am
Are there any other object security types used e.g. Cell Security?
Yes but not in combination with Version dim.
I hope I'm clear enough now, sorry for misunderstanding...