Current Behavior
Model Security controls which members users can access through queries and writeback.
When an XL report is generated, Model Security is applied when the query retrieves members. However, if a Drill Indicator is used, the parent member is then expanded into its children based on the hierarchy without re-applying Model Security.
As a result, restricted children or descendants may still be displayed through the Drill Indicator.
Enhancement Request
We would like Model Security to work consistently between queries and XL report functions.
- Apply Model Security when members are expanded through the Drill Indicator.
- Provide an option to control whether restricted descendant values are included in the parent total.
Business Impact
Users may see restricted members or data through drill expansion even though they cannot access them through the original query.
Consistent security behavior would help prevent unintended data exposure and make access control easier to manage.
