TM1 Forum

Is there an easy way in TM1 to lock down prior months? I don't want users to be able to change data in months that are closed. Is there a best practice for this or is changing the security to read only for a given dimension the way to go?

ChrisF79 wrote:is changing the security to read only for a given dimension the way to go?

What is the particular issue with changing the security in the Month Dimension's element security cube?... it's simply a matter of changing cells from read to write?

If you wanted you could create a TI Process which you run at month end (possibly via a scheduled chore)
Depending how your month ends actually fall (eg. if they are actually by month or 4-4-5 basis etc.) you could set a parameter for "Current Period" either picking up from a specified plan or time stamp (could possibly use now() with a bit of formatting)... if the month end rollover is a bit less regular however you could simply run the process and add the parameter manually.
Regardless the TI would make sure that current and future periods are set to Write and all others are set to read for the required security groups.
ElementSecurityPut Ti function or a CellPutS directly to the }ElementSecurity cube will do, also worth scanning over the SecurityRefresh function in the documentation.

Then of course the }ElementSecurity cube can be updated via rules looking at some sort of control cube.


If you give the more specific problem/dislike you have to the "natural" method I am sure people will be able to give more specific advice.

The are a few options here but the most common are locking security down by either rules or TI. Either way normally involves using a control cube to dictate what and when lock down. Using rules (on the security control cube) usually means you have to refresh security either manually or via TI. Using the TI method means you don't have to do that but you do have to execute the process.

I hope that helps,

Jim.

Both answers helped a lot. Thanks for the fast reply.