m1013459New Member10 years agoStatus: CompletedColumn Level Security for reports Ability to define rules at column level, to control the data fields available to different roles (e.g. employee salary visible to the users in finance roles only, while other employee details visible...Show More
Recent ideasAll Idea StatusesNewNeed ClarificationNeeds VotesUnder ReviewPlannedCompletedAbandonedTagged:TagMost RecentAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...Visual Type Defaults in Visualization Pane This would change my life with fussy clients and client/public facing apps. In addition, it would allow me to add more value to the clients on retainers who do not have the 'hours' to allocate to...List slicer (preview) Would be nice to have posibility to put value on side and to add more values in columns) ... like was in Attribute slicer Slicer - Select leafs only Hello, Is it possible to add a feature for the slicer when using a hierarchy to be able only to select leafs only for the single selection mode ? Many thanks Add a Close or “Return to previous page” button to Semantic Model Security and Settings pages When updating RLS group assignments through Semantic model > Security, there is no consistent in-product Close or Done button that returns the user to the previous workspace view. The browser Back b...
