Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
Hi all,
I'd like to scale the range of the secondary (line) Y-axis in a manner that provides a descriptive visual; to do that, I set the range to. (-30,20). This scaling provides a great visual, but I want to remove half of the axis value callouts. See red box in attached image.
If the correct range (0,20) was used for the line (2nd Y-axis), then it overlaps with the bar graphics and does not look as good. Is there a way to remove the callouts for -10x, -20x, and -30x or start the callouts at 0x?
Is there a simple solution for this?
Thanks!
Solved! Go to Solution.
Hi @EHaft
Technical Answer:
Since there is no option for conditional formatting of axis labels, there is no way to hide some of the labels.
One workaround is to place a white rectangle over them, but this rectangle will be static. Therefore, if the proportions of the chart change, some of the labels may reappear.
Effective Data Visualization Perspective
This chart presents several challenges for user interpretation, as it goes against some fundamental principles of visual perception. Let me explain with a few examples:
1. Three Different Metrics
The chart combines costs, revenue, and profit in one visualization. When multiple metrics are presented together, users may inadvertently group them (Gestalt principles), especially in a stacked format. This is particularly problematic because costs and revenues shouldn’t be interpreted as cumulative values. While it’s true that these metrics are part of an overall picture, they remain distinct measures, and presenting them together in this way can lead to confusion.
2 Use of Dual Axes
The line chart being positioned above the bars can lead to misinterpretation. In our perception, elements higher on the chart are perceived as larger or more important. However, in this case, the line represents a completely different scale, which could cause users to misjudge the actual values.
3. Misuse of a Line Chart
Line charts are most effective for showing trends or changes over time, where the angle and direction of the line convey meaning. However, in this chart, the comparison is not temporal but categorical—ranking products by profitability. As a result, the use of a line chart may lead users to interpret it incorrectly as showing trends, rather than rankings.
These are just some of the challenges with this visualization.
Recommendation:
I suggest considering an alternative visualization, such as a combination of a table and separate bar or column charts. This approach would:
Maintain the relationship between the metrics while avoiding confusion.
Present accurate comparisons by separating the three rankings.
Ensure each metric is visually distinct, improving clarity for the user.
Of course, this is entirely up to you. A file with two suggested examples is attached for your review.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Hi @EHaft ,
In addition to Ritaf1983's method, you can also try changing the minimum of the line y-axis under visual format.
Hope it helps.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @EHaft
Technical Answer:
Since there is no option for conditional formatting of axis labels, there is no way to hide some of the labels.
One workaround is to place a white rectangle over them, but this rectangle will be static. Therefore, if the proportions of the chart change, some of the labels may reappear.
Effective Data Visualization Perspective
This chart presents several challenges for user interpretation, as it goes against some fundamental principles of visual perception. Let me explain with a few examples:
1. Three Different Metrics
The chart combines costs, revenue, and profit in one visualization. When multiple metrics are presented together, users may inadvertently group them (Gestalt principles), especially in a stacked format. This is particularly problematic because costs and revenues shouldn’t be interpreted as cumulative values. While it’s true that these metrics are part of an overall picture, they remain distinct measures, and presenting them together in this way can lead to confusion.
2 Use of Dual Axes
The line chart being positioned above the bars can lead to misinterpretation. In our perception, elements higher on the chart are perceived as larger or more important. However, in this case, the line represents a completely different scale, which could cause users to misjudge the actual values.
3. Misuse of a Line Chart
Line charts are most effective for showing trends or changes over time, where the angle and direction of the line convey meaning. However, in this chart, the comparison is not temporal but categorical—ranking products by profitability. As a result, the use of a line chart may lead users to interpret it incorrectly as showing trends, rather than rankings.
These are just some of the challenges with this visualization.
Recommendation:
I suggest considering an alternative visualization, such as a combination of a table and separate bar or column charts. This approach would:
Maintain the relationship between the metrics while avoiding confusion.
Present accurate comparisons by separating the three rankings.
Ensure each metric is visually distinct, improving clarity for the user.
Of course, this is entirely up to you. A file with two suggested examples is attached for your review.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
78 | |
76 | |
53 | |
37 | |
31 |
User | Count |
---|---|
101 | |
56 | |
51 | |
45 | |
40 |