KB230323: In MicroStrategy Analytics Enterprise, security filter is incorrectly applied in a view report, when the security filter attribute and metric’s fact entry level have M:M relationship

SUMMARY
This issue has been classified as a defect by Strategy. The impact is limited to Strategy Analytics Enterprise 9.x-10.x when security filter attribute and metric’s fact entry level have a M:M relationship. A solution/code fix for this issue is not available in current releases but is expected to be available in the next major Strategy release.
SYMPTOM
In Strategy Analytics Enterprise 9.x-10.x, security filter is incorrectly applied in a view report (based on an Intelligent Cube) when the security filter attribute and metric’s fact entry level have a M:M relationship.
In cases where the security filter attribute is not related to the fact entry level of the metric or to any attributes on the grid, the security filter will be ignored and the metrics will be displayed to the user.
M:M is treated as no relation from engine point of view. When security filter attribute and metric’s fact entry level have M:M relationship, the metric value is incorrectly suppressed.
Refer to the following Strategy Knowledge Base document for more information on security filter application rules in Strategy Analytics Enterprise 9.4.1
KB45569 : Security filter application in documents using Intelligent Cubes as datasets in Strategy Analytics Enterprise 9.4.1
STEPS TO REPRODUCE 
The steps below are based on the Strategy Tutorial project
 

• Create an Intelligent Cube named Q1 with attribute 'Item' and metric 'Cost'.
• Publish Intelligent Cube Q1.
• Create a view report named R1 from the published Q1 and put both Item and Cost on the grid.
• Create a security filter named SF1 with 'Catalog=2012 winter'.
• Create a user named SF1 with necessary privilege and apply the security filter SF1.
• Log in with user SF1 and run report R1.
• Notice that no data is returned for the metric Cost.
  

• The SQL view shows security filter is ignored for the grid attribute but the metric value is suppressed.
   
  

  
  select      [Item]@[ITEM_ID],                                     [Item]@[ITEM_NAME]                                      from         Q1 

  
  

CAUSE
 
This is a known issue with Strategy Analytics Enterprise 9.x-10.x.
The metric 'Cost' is based on fact 'Cost', and one of its fact entry level attribute is 'Item'. Security filter attribute 'Catalog'  has a M:M relationship with the metric’s fact entry level 'Item' and this should be treated as unrelated and hence the security filter should be ignored. However, it is not ignored and the metric value is suppressed. Security filter is properly ignored when security filter attribute 'Catalog' has a M:M relationship with the grid attribute 'Item'.
ACTION
Contact Strategy Technical Support for an update with this issue.This issue is expected to be addressed in the next upcoming major Strategy release. 
The Strategy Internal Reference Number for the issue discussed in this technical note is DE58961.