Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
KGBOR
Helper I
Helper I

Issues calculating individual results

Hello Power BI Community,

 

I'm having the following situation: In a given report I was expected to calculate on a team level how many % of the cases (these are interactions between operators and customers) are being resolved on the same day (if resolved on the same day, value is 1 if not then it is 0) vs the total incoming cases.  

 

On a team level this was not a problem, however when I wanted to break it down to individual level I realized that there might be discrepancies in the numbers vs what happens in reality. The thing that is causing this discepancy is the fact that even though a case might be opened by one operator, it could be resolved by another one. It means I cannot just group it by the "Created By" column as it will not reflect the reality. You can see below a mock of the data I have and also the basic pivots that showcases the problem. To make it more complicated the system from which I'm pulling the data from, are displaying the operators in 2 different ways, in the "Created By" column by the domain ID and in the "Resolved by" one with their full name.

 

As you can see below in the raw data Lisa Smith resolved 5 cases however in the Pivot, and this is exactly what happens in PowerBI as well, only 4 of them shows up if I use the column "created by".

 

KGBOR_0-1673537773481.png

 

Any suggestions how to approach this? Thank you!

1 ACCEPTED SOLUTION
Greg_Deckler
Super User
Super User

@KGBOR So just used Resolved By instead?



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
Power BI Cookbook Third Edition (Color)

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

2 REPLIES 2
Greg_Deckler
Super User
Super User

@KGBOR So just used Resolved By instead?



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
Power BI Cookbook Third Edition (Color)

DAX is easy, CALCULATE makes DAX hard...

Hi @Greg_Deckler ,

 

If I go with Resolved by, I'm removing all the cases from the denominator which are not resolved. So what I'd need is a measure which sums up all the tickets the indivudal resolved and another one which sums up all the ones which they created. 

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

November Carousel

Fabric Community Update - November 2024

Find out what's new and trending in the Fabric Community.

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.