Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Good morning everyone,
I am having a strange issue with a Guage Visual where when I use a slicer to filter on Salesperson the Target Disapears.
For context.......
Data Model
SalesTransaction Table (1 row per sales Transaction)
- Billing Date joined to DateTable
- Custom Column (year of Billing Date||SalesPersonID) as GoalKey joined to SalesmenGoals table.
SalesmenGoals table has one row / year / sales person id.
Target Properly Sums the Used Sales Goal when no salesperson is selected.
Tarrget Disapears when a sales person is selected but you can see from the card visual that its properly finding the amount.
So this should show a target of 6.1 m as seen in the card.
I don't understand what is going on.
I have used the Used Sales_$ from the Goal table
Created a sum measure in the Goal table
Created a sum measure in the Transaction table.
Created a related column in the Trans table.
Then a measure on that.
I don't get why the card picks up the 6.1m correctly from the filter context but he Guage drops the Target line whenever I pick any salesperson.
One thing to note is that I have used both the Salesperson from either table in the slicer with the same results.
Only difference is that I have to set the slicer direction to both when using the trans table salesperson field for the card to change when salesperson is filtered.
Using Trans[Salesperson] is my preference for the slicer as some sales people don't have goals.
Anyhow, the card showing the correct sum for the context and the guage dropping the target line is driving me nuts. Doesn't make sense. I appreciate anyones time who might have some insight into what the problem is.
Solved! Go to Solution.
Hi @jkourtesis7 ,
To correctly set up the maximum value for your gauge, you'll need to define a specific maximum value. The issue you're experiencing is that, by default, Power BI sets the gauge’s maximum value to double the measure you’ve placed in the gauge’s value field.
In your first example, the target appears correctly because it’s less than twice your Gross Sales. However, in the second example, the target is higher than twice the Gross Sales, which prevents it from displaying correctly. To fix this, you should create a measure to set this maximum (MAX) value using a conditional logic.
Here’s a measure you can use:
Max Value =
IF(
[Target] >= [Sales Amount],
[Target],
[Sales Amount]
)
This measure checks if the target is greater than or equal to the sales amount. If it is, it sets the target as the maximum; otherwise, it sets the sales amount as the maximum.
After creating this measure, drag it into the "Maximum Value" field of the gauge, as shown in the image below.
I hope this help you, if yes, please make sure to give a kudo and accept as solution
Hi @jkourtesis7 ,
To correctly set up the maximum value for your gauge, you'll need to define a specific maximum value. The issue you're experiencing is that, by default, Power BI sets the gauge’s maximum value to double the measure you’ve placed in the gauge’s value field.
In your first example, the target appears correctly because it’s less than twice your Gross Sales. However, in the second example, the target is higher than twice the Gross Sales, which prevents it from displaying correctly. To fix this, you should create a measure to set this maximum (MAX) value using a conditional logic.
Here’s a measure you can use:
Max Value =
IF(
[Target] >= [Sales Amount],
[Target],
[Sales Amount]
)
This measure checks if the target is greater than or equal to the sales amount. If it is, it sets the target as the maximum; otherwise, it sets the sales amount as the maximum.
After creating this measure, drag it into the "Maximum Value" field of the gauge, as shown in the image below.
I hope this help you, if yes, please make sure to give a kudo and accept as solution
Oh I see it now. You are awesome thank you very much 🙂
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
94 | |
92 | |
83 | |
71 | |
49 |
User | Count |
---|---|
143 | |
121 | |
111 | |
59 | |
57 |