Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
I have two tables, Applications and Closing Reports. They have two inactive relationships between the two tables.
I need to calculate the turnaround time between the response date and the start date and created a measure, however, the measure isn't quite correct and I'm not sure how to optimize it to get the correct result.
The measure is this:
The measure is calculating correctly at 48 days when shown in a table graph, though the total shows 14:
However, once I bring the turnaround time (the measure) into a bar graph, the results are incorrect and show the 14 days:
Unfortunately, I cannot attach the .pbix file, so I'm hoping someone can help with this issue.
Thanks in advance!
Solved! Go to Solution.
As far as I can see the issue here is your measure works in the body of the table because there is the context of job name / IDs that allow the userrelationship context to work.
The total row and the bar graph lack that context so the measure is returning the "wrong" value.
My suggestion would be to create a calculated column in either of your tables that returns the date difference for each row context.
Proud to be a Super User! | |
thanks for your concern about this issue.
Your answer is excellent!
And I would like to share some additional solutions below
I am glad to help you.
According to your description you are using the created measure in table and it is displaying fine, but not in card!
This is a very common problem, because it has to do with the computational environment in which the measure is placed (when you put the measure directly into the card, it actually shows the value of the total)
like this:
When you use a measure or calculate column, the card will always show the total value.
(power bi will show the aggregated value)
Here are my suggestions
1. add a slicer (the external filter way)
2. Add filters to the dax code (add internal filters)
measure is affected by filters in the current visual and filters in the dax code as well as external filters (slicers)
while calculate column is affected by the row context (current row)
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
thanks for your concern about this issue.
Your answer is excellent!
And I would like to share some additional solutions below
I am glad to help you.
According to your description you are using the created measure in table and it is displaying fine, but not in card!
This is a very common problem, because it has to do with the computational environment in which the measure is placed (when you put the measure directly into the card, it actually shows the value of the total)
like this:
When you use a measure or calculate column, the card will always show the total value.
(power bi will show the aggregated value)
Here are my suggestions
1. add a slicer (the external filter way)
2. Add filters to the dax code (add internal filters)
measure is affected by filters in the current visual and filters in the dax code as well as external filters (slicers)
while calculate column is affected by the row context (current row)
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
As far as I can see the issue here is your measure works in the body of the table because there is the context of job name / IDs that allow the userrelationship context to work.
The total row and the bar graph lack that context so the measure is returning the "wrong" value.
My suggestion would be to create a calculated column in either of your tables that returns the date difference for each row context.
Proud to be a Super User! | |
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
106 | |
75 | |
45 | |
41 | |
32 |
User | Count |
---|---|
170 | |
90 | |
65 | |
46 | |
44 |