I want to restrict data entry in 2013 , Q1 and Q2 . But 2014, Q1 and Q2 want to keep open.
have two dimension “ DimYear” and “ DimQuarter”
In “DimYear” two element 2013 and 2014
In “DimQuarter” four Element Q1,Q2,Q3,Q4
I tried with Element level Security in DimQuarter (Q1(R) , Q2(R) , Q3(W), Q4(W).
And DimYear Dimension 2013(W) and 2014 (W)
In that case 2013 Q1 and Q2 are locked that's fine which i want to ,
but also locked 2014 Q1 and Q2, Which i don't want.
Any solution please ?
Dimension Security.
- qml
- MVP
- Posts: 1096
- Joined: Mon Feb 01, 2010 1:01 pm
- OLAP Product: TM1 / Planning Analytics
- Version: 2.0.9 and all previous
- Excel Version: 2007 - 2016
- Location: London, UK, Europe
Re: Dimension Security.
What you are describing in your post is actually Element Security, not Dimension Security as the thread title suggests. In your case, however, you need to be looking at implementing Cell Security, a subject you will find plenty on in the documentation and on this forum.
Kamil Arendt
-
- Posts: 33
- Joined: Tue Jan 29, 2013 2:52 pm
- OLAP Product: TM1
- Version: 9.0 SP3 9.5.1 10.1.1
- Excel Version: excel 2010 2007 2003
Re: Dimension Security.
Apologies for hijacking the thread with a personal agenda. Am I alone in hoping that a new security paradigm is in the TM1 future roadmap?
Cell security works, but can result in a large cube. All to often I come accross cases where you just need security over two dimensions, but your cube may have significantly more. Element security will not work for the reasons detailed above and cell security means that you have to put security over all dimensions, which seems a less that inutative way of using the TM1 resources. This is especially true if you run one instance with sufficient security groups for all your needs.
If anyone else thinks that a two or three dimension (plus the '}groups' dimension) security cube would be a significant resource save, I would beinterested to hear any thoughts and responses.
Cell security works, but can result in a large cube. All to often I come accross cases where you just need security over two dimensions, but your cube may have significantly more. Element security will not work for the reasons detailed above and cell security means that you have to put security over all dimensions, which seems a less that inutative way of using the TM1 resources. This is especially true if you run one instance with sufficient security groups for all your needs.
If anyone else thinks that a two or three dimension (plus the '}groups' dimension) security cube would be a significant resource save, I would beinterested to hear any thoughts and responses.
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Dimension Security.
Couldn't agree with you more, it would be a very nice enhancement to allow cell-level security on something less than a complete cube, where all the other dimensions in the cube default to no security. I just don't see it happening. IBM is devoting all their time to making TM1 a more marketable product, not a better one.cgaunt wrote:If anyone else thinks that a two or three dimension (plus the '}groups' dimension) security cube would be a significant resource save, I would beinterested to hear any thoughts and responses.
