Database security: Cube visibility

mcanestrari

In the "Database Security" section, we have noticed that if we use cube visibility to define user action perimeters, it works everywhere except in dataflows.

This behavior, despite being documented in the manual, seems quite illogical because if the functionality helps in profiling security profiles in a faster and more reliable manner, thereby eliminating the need for controls in each procedure, I do not see why it should not work in dataflows.

In conclusion, our request is to make cube visibility work for all actions that a user can perform, or at least provide a function that can define an action perimeter for users, and ensure that this perimeter applies throughout the entire application.