Security Filter Question

[OV]

Hi,

I have the following situation. In a project, I have two completely unrelated fact tables. Different users can see
different slices of data from each table. The only way I believe I can controll that is by creating security filters. The problem is that if I can have only one security filter per user. If I create a security filter with two conditions(one for each table), microstrategy tries to apply both conditions against each fact table.
Has anyone had this situation before? Of course I can separate the project in two but that will be a lot of work at this point.
Any ideas are appreciated.

Thanks, OV

 

[JRO061601]

If the condition in the security filter does not apply to the query being generated, I was under the impression that it shouldn't be called.

If this isn't true, then maybe the attributes you are filtering are not modeled independently of each other? In other words, if you have condition A and condition B, and Fact Table X and Fact Table Y, maybe the engine thinks it needs to apply both A and B to X and Y. Something to dig into.

One other thought is to change the operator in your security filter to 'OR'. By default it is 'AND', and maybe that is tripping you up.

Another way to limit what data a user sees would be to leverage database security views and individually map MicroStrategy logins to database logins. Obviously this would create a lot more administrative overhead, so maybe consider this last.

Please let us know what you come up and/or what works.