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 RecentMake workspace and item session persistence optional Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...Support Encrypted Sensitivity-Labeled Excel Files in Power Query Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...Auto-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
