Page 1 of 1

Warning - read only users

Posted: Thu May 24, 2018 11:21 am
by Wim Gielis
Hello,

Just one thing I noticed while restricting TM1 users to read-only.
There is a property in the }ClientProperties cube for that. Just set it to 1 for read only.

However, if you do this to yourself, for example being TM1 admin person, you can also remove write rights from yourself / admin persons.
I was caught like that. What helps is writing a TI process to do a CellPutN of 0 in the relevant cell of the }ClientProperties cube. Execute it and you're good again.

Best regards,

Wim

Re: Warning - read only users

Posted: Thu May 24, 2018 5:25 pm
by jim wood
Good to know. Thanks Wim,

Jim.

Re: Warning - read only users

Posted: Mon Jun 04, 2018 2:01 pm
by MGrain
I've been there and done that too, caused a moment of panic!

I added a rule to the }ClientProperties cube to set myself back to zero.

Re: Warning - read only users

Posted: Tue Jun 05, 2018 3:05 pm
by tm123
The other problem with Read Only Users is that the Write-Back will be completely disabled for them. I know we can't complain about this, but since in my models I usually create a cube to store User Selections and use those Selections in MDX Subsets (for example to implement Cascaded Prompts), that becomes an issue

Re: Warning - read only users

Posted: Wed Jun 06, 2018 8:00 am
by orlando
tm123 wrote: Tue Jun 05, 2018 3:05 pm The other problem with Read Only Users is that the Write-Back will be completely disabled for them. I know we can't complain about this, but since in my models I usually create a cube to store User Selections and use those Selections in MDX Subsets (for example to implement Cascaded Prompts), that becomes an issue
Just a quick thought about your issue.
Maybe you could "talk" to this cube via a TI (which read only users can execute). if they can't write ito a cube by the process, it should work to execute runti. the process run via runti (context of an user with hiher rights) could than handle your parameters.

Re: Warning - read only users

Posted: Wed Jun 06, 2018 1:30 pm
by tm123
orlando wrote: Wed Jun 06, 2018 8:00 am
tm123 wrote: Tue Jun 05, 2018 3:05 pm The other problem with Read Only Users is that the Write-Back will be completely disabled for them. I know we can't complain about this, but since in my models I usually create a cube to store User Selections and use those Selections in MDX Subsets (for example to implement Cascaded Prompts), that becomes an issue
Just a quick thought about your issue.
Maybe you could "talk" to this cube via a TI (which read only users can execute). if they can't write ito a cube by the process, it should work to execute runti. the process run via runti (context of an user with hiher rights) could than handle your parameters.
In my case, in every websheet that requires to cascade prompts, every time the user changes a SUBNM Selection, I have a DBSS that saves the Selected Member in my cube, which works perfect, and I do this not only to make the UI more user friendly, but even to avoid selection of Invalid Intersections. Doing this with a TI process, would require to have an action button clicked every time the user changes any of SUBNM selections.

It would be nice if this READ-ONLY user, does not stop the user from writing to a }Clients base cube

Re: Warning - read only users

Posted: Wed Jun 06, 2018 2:16 pm
by orlando
tm123 wrote: Wed Jun 06, 2018 1:30 pm It would be nice if this READ-ONLY user, does not stop the user from writing to a }Clients base cube
yep. that's true. or ibm should have never introduced them (instead made better prices for a "normal" user)