It would be nice to be able to track code analysis issues produced during the build. I'd want to be able to group by different categories to see if we are getting better over time. Bonus: Determine what CA rules are actually enabled by inspecting the project files in the source code.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Feature Request: Add a Warning Prompt Before Deleting Tables That Contain Measures
Problem Statement: In Power BI, measures are linked to specific tables. When a developer deletes a table from the model view or report view, Power BI automatically deletes all measures assigned to ...Murtaza_Ghafoor2 hours agoSuper UserNew8Views1like0CommentsCustom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON4 hours agoNew MemberNew8Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi5 hours agoMicrosoft EmployeeNew23Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull227 hours agoAdvocate INew32Views1like1Comment