SYMPTOM
When using the OR qualifier on a report based off a cube some users may experienced unexpected results when using multiple security filters with the OR qualifier.
STEPS TO REPRODUCE
In Strategy Tutorial
1. Create a security filter on Category as well as Region with an “OR” statement between the filters
2. Apply the security filter to a test power user account that was applied the security filter
3. Create a cube with Call Center and Profit
4. Create a report based of the cube and no data is returned. Although the security filter suggest at least profit for the Region of Atlanata should be returned as an OR filter was used
CAUSE
This behavior is expected based on our current design for Security Filter.
Based on our current design, the engine first checks whether there is any attribute in the security filter which does not have any relationship with Cube Attributes. In this step, we found that Category does not have any relationship with Cube Attributes.
In the next step, it checks whether all the attributes in the security filter has any relationship with the Metric's Entry Level on Cube. In this case, Profit's Entry Level is Catalog, Day, Days to Ship, Employee, Item, Order, and Phone Usage. All the Attributes in the security filter have a relationship with Profit's Entry Level.
In this case, the engine marks the NA flag for that Metric, and Profit Metric will not be generated in CSI (Cub Subsetting Instructions) statement, and that value will not show up in report.
The reason is that if the security filter attribute has relationship with Metric Entry Level attributes, and that the security filter attribute is not on the Cube template, causing the Data Leak in most of the cases. Despite the fact that for this simple case such as this it will not case the Data Leak because the security filter expression is a simple OR statement.
ACTION
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release.
WORKAROUND
Create a new Fact Profit2 which Metric Entry Levels does not have any relationship with Category. You can create it by manually define the Source Tables to make sure Metric Entry Levels does not have any relationship with Category.
KB441410
