Hey all,
Newbie here, so anything I type below may or may not make any sense to any other than me! lol. When i say not working, i mean 'working' the way I anticipate it to work based on the Technotes and other information i have been able to gleen from their (MSTR) website. A little background on what I am trying to accomplish. I have been tasked with trying to assess/alter our current security implementation and one of the items i am looking at is object level permissions (to objects within the public folder, as well as certain attribute levels).
For example, when a user runs report A, at the highest level is 'Carrier' information. If you try to drill down on 'Carrier' you have the option of drilling to 'Account', 'Group', and 'Member'. Currently, everyone can drill down to everything (as i understand it, within their appropraite data sets). In reality, only some people should be able to drill down to the member level. So I am trying to limit this with security filters (am i on the right path?). So what I have done is created a filter that says user 'Joe Schmoe' can access these carriers (A,b,c).
I then created a security filter for Joe Schmoe and set the Top range attribute to 'Carrier' and the Bottom Range attribute to Group (or Member, wasn't sure if bottom range indicates the last level you can see or the first level you can't see). But Jo Schmoe can still drill away till he is on the member level. Can any one point me in the right direction? Thanks in advance.
Ray H.
I'd give my right arm to be ambidextrous.
BTW, I am not sure if this makes a difference but i noticed that the Security model is set to 7.1x and not 7.2 even though we are using 7.2 under project configuration. Does MSTR require the newest( 7.2) security model to handle security filters??
Newbie here, so anything I type below may or may not make any sense to any other than me! lol. When i say not working, i mean 'working' the way I anticipate it to work based on the Technotes and other information i have been able to gleen from their (MSTR) website. A little background on what I am trying to accomplish. I have been tasked with trying to assess/alter our current security implementation and one of the items i am looking at is object level permissions (to objects within the public folder, as well as certain attribute levels).
For example, when a user runs report A, at the highest level is 'Carrier' information. If you try to drill down on 'Carrier' you have the option of drilling to 'Account', 'Group', and 'Member'. Currently, everyone can drill down to everything (as i understand it, within their appropraite data sets). In reality, only some people should be able to drill down to the member level. So I am trying to limit this with security filters (am i on the right path?). So what I have done is created a filter that says user 'Joe Schmoe' can access these carriers (A,b,c).
I then created a security filter for Joe Schmoe and set the Top range attribute to 'Carrier' and the Bottom Range attribute to Group (or Member, wasn't sure if bottom range indicates the last level you can see or the first level you can't see). But Jo Schmoe can still drill away till he is on the member level. Can any one point me in the right direction? Thanks in advance.
Ray H.
I'd give my right arm to be ambidextrous.
BTW, I am not sure if this makes a difference but i noticed that the Security model is set to 7.1x and not 7.2 even though we are using 7.2 under project configuration. Does MSTR require the newest( 7.2) security model to handle security filters??