Security Filters

[robo100]

I am trying to create a report that displays all the company regions sales totals. I would like to add some security such that if Region 1 Manager runs the report he or she will be able to see there totals aswel as totals for the other regions, but only be able to drill down on there particular region.

I have had a look at security filters, but I am not having much luck with the objective above.

Any help would be greatly appreciated.

Thanks in advance.

 

[chael]

Ok - create 2 metrics...one with report level dimensionality for sales, and one with absolute dimensionality for sales at the company level. Put them both on the report and then maybe set up the drilling (via the drill map editor) however you want -- drill to template, etc..

 

[chael]

oh, yeah...my solution above assumes that the security filter is already in place. Creating security filters is pretty easy. Create the filter you want to use first, then edit the user, assign the security filter to that user, then run the report.

Be sure to check out the knowledge base. There are many useful TNs in there that will help you solve this.

 

[robo100]

Thanks for your reply. I think I may have confused the requirements in my previous post. I'll try an be clearer with the following example. Assume I am logging in as Region 1 Manager. What I would like to see is the following, with drilling only possible on Region 1.

Sales
Region 1 10,000
Region 2 9,000
Region 3 8,000

What I actualy see with security filter defined as region in list Region 1 is the following.

Sales
Region 1 10,000

I have posted this with tech support who have stated that this is not possible out of the box and that it will be logged as a future enhancement. However I still wait in hope that somebody out there may be able to prove it is possible.

 

[JRO061601]

For what it is worth, this functionality has been an enhancement for several years now, probably since soon after the release of MSTR 7. The request is simple enough but I imagine the implementation is somewhat complex. Not to mention, if using this, a ton more work for the administrator. One would probably have to specify in each hierarchy in the project which level a given user cannot see beneath and for which attribute elements. Otherwise there are workarounds within the model to see another region's broken down numbers even when you aren't supposed to.