Dynamic subset, can it be locked?

[pmakulski]

I have a dynamic subset that makes reference to a value in the }ElementATtributes}clients} cube. It limits the subset to what the user wants to see.
I actually did this for performance reasons, and it has helped a great deal.

But, from time to time, the mdx statement disappears from the view and becomes static. I assume somebody with admin rights is doing it (me perhaps, and a very short list of others). WHen the subset errantly becomes static, I find out when users start complaining.
If it is me accidentally doing it, I never see a confirmation request (do you want to save your changes), so I never know when/why this happens.

Is there any way to lock a subset definition so that it can't be changed, unless it is explicitly unlocked?

Thanks.

[jim wood]

You could always add a TI process to rebuild the subset each night which won't help during the day that it is over-written but it will stop it staying static,

Jim.

[tomok]

You could also try setting the properties of the .sub file in the data directory to READ ONLY. This would stop TM1 from being able to save the sub file. Don't know what that would do to the live subset in TM1, never tried it, but it MIGHT work.

[lotsaram]

You could also try setting the properties of the .sub file in the data directory to READ ONLY. This would stop TM1 from being able to save the sub file. Don't know what that would do to the live subset in TM1, never tried it, but it MIGHT work.

I agree it might work (in fact it probably would) but I'd sure want to test it in a non-prod environment. As the TM1 server operates on the assumption that it has exclusive and unrestricted access to all files within the data directory weird things can happen when those files get messed with in the file system outside of TM1 while the server is in session. It may be fixed now in 9.5 but I can remember there were stability issues (i.e. crashes) in 9.1 and 9.4 if public subsets were changed or deleted in the file system.

The real and best fix here I think is to make sure everyone with admin access is sufficiently trained and aware NOT to click on "Yes" to the prompt that subset X has been modified do you want to change it? OR to ensure that anyone without sufficient training to grasp this is NOT a member of the admin group.

[pmakulski]

Setting file property to read-only...
Yeah I had thought of that, but was afraid it would cause trouble.
Sounds like it likely would (cause trouble). So, I'm not trying it
If anybody does try it, please report back.