In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
in the current state, when Selective Access is enabled on hierarchical lists, users are restricted to viewing only the list members they have been granted access to. While this works well for controlling leaf-level visibility, it also impacts how summary values (parent-level totals) are calculated and displayed.
Specifically:
Users can only see data for the leaf items they have access to.
Parent-level totals (summaries) are not appropriately displayed as per the access.
This results in incomplete or misleading aggregates at higher levels of the hierarchy, which creates challenges for reporting and analysis.
In the current state only workaround seems to be adding User dimension to the modules, but this increases the size astronomically.
How often is this impacting your users?
This behavior is consistently observed in models where selective access is applied to hierarchical dimensions used for reporting which impact a lot of important reports
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Business/end users consuming summarized reports, Model builders and solution architects, Workspace administrators managing access and reporting
What would your ideal solution be? How would it add value to your current experience?
Introduce a configurable option to decouple summary calculations from selective access, such as:
A setting that enables “secure leaf access with appropriate parent aggregation”
Please include any images to help illustrate your experience.
