To make life easier, I am suggesting a secondary colour be used to help identify additional fields or measures that are somehow connected to the selected visual. Whether that be callout values, reference labels, filters, conditional formatting etc.
Perhaps a secondary colour (grey in this example) to help differentiate.
No CommentsBe the first to comment
Recent ideas
actor_user_id / actor_user_name in Delta history is not captured.
The actor_user_id /actor_user_name are currently displaying a null. These are visible only when the parameter - spark.microsoft.delta.describeHistory.runtimeEnvironmentFields.enabled=true is set. But...rajorshidas0122 minutes agoNew MemberNew3Views0likes0CommentsFeature Proposal: Universal BI Translation and Semantic Equivalence Engine for Microsoft Power BI
Feature Proposal: Universal BI Translation and Semantic Equivalence Engine for Microsoft Power BI Category: Power BI / Microsoft Fabric / AI-Assisted BI Modernization 1. Executive Summary I propos...timster0076 hours agoNew MemberNew2Views0likes0CommentsSelect Entire Hierarchies in Power BI Personalize Visuals
Feature Request: Select Entire Hierarchies in Power BI Personalize Visuals Hi Power BI Team, I'd like to suggest an enhancement to Personalize Visuals that allows users to select an entire hierarch...davejames1211 hours agoNew MemberNew11Views1like0CommentsFile level commit - Need the ability to edit the commit description
I tried the recently announce file level commit for Fabric items. One notable issue I have with the feature (testing this with a Fabric warehouse, I'm assuming this would hold true for other items): ...DataBard12 hours agoMost Valuable ProfessionalNew31Views0likes2Comments