gregor_prohask1
11 years agoNew Member
Status:
New
Attribute-based (Column-Based) Security for SSAS (OLAP)
It would be handy to secure attributes in SSAS OLAP in a way that confidential attributes are only shown to a specific user group. Example: if you take customer-dimension in Adventure-Works attribute "birth date". (out of simplification) all user should be able to see all customers but only some users should be able to "see" birth-date. An allowed User should be able to show "birth date" as a propertie of costumer. if a restricted user opens the same report attribute "birth date" shouldn't be shown at all but still all other customer-related informations.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande9 hours agoNew MemberNew180Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes17 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v17 hours agoCommunity ChampionNeeds Votes37Views2likes1Comment