Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Everyone,
I have three different summarized tables in my data model which represent user incoming calls handled, outbound calls, cases closed and I have one more table which is user login hours.
I am trying to calculate the Productivity score of every user by using (calls handled + outbound calls + cases closed ) / Login Hours
Tables incoming calls handled, outbound calls, cases closed looks like below.
Calls Handled
user | calls_handled | User-work-day |
UTYAA14 | 10 | UTYAA14-2019-10-11 |
UTYAA15 | 6 | UTYAA14-2019-10-12 |
UTYAA16 | 8 | UTYAA14-2019-10-14 |
UTYAA17 | 9 | UTYAA14-2019-10-15 |
UTYAA18 | 4 | UTYAA14-2019-10-16 |
Outbound Calls
user | outbound_calls | User-work-day |
UTYAA14 | 2 | UTYAA14-2019-10-11 |
UTYAA15 | 4 | UTYAA14-2019-10-12 |
UTYAA16 | 5 | UTYAA14-2019-10-14 |
UTYAA17 | 1 | UTYAA14-2019-10-15 |
UTYAA18 | 4 | UTYAA14-2019-10-16 |
Cases_Closed
user | Cases_closed | User-work-day |
UTYAA14 | 20 | UTYAA14-2019-10-11 |
UTYAA15 | 11 | UTYAA14-2019-10-12 |
UTYAA16 | 12 | UTYAA14-2019-10-14 |
UTYAA17 | 7 | UTYAA14-2019-10-15 |
UTYAA18 | 4 | UTYAA14-2019-10-16 |
User login Hours
user | Login Hours | User-work-day |
UTYAA12 | 8 | UTYAA12 - 2019-10-11 |
UTYAA13 | 7 | UTYAA13- 2019-10-12 |
UTYAA14 | 9 | UTYAA14 - 2019-10-13 |
UTYAA15 | 9 | UTYAA15 - 2019-10-14 |
UTYAA16 | 10 | UTYAA16- 2019-10-15 |
UTYAA17 | 7 | UTYAA17 - 2019-10-16 |
I've created a relationship between user login hours to all three tables using User-work-day and I tried to create a column (calls handled + outbound calls + cases closed ) / Login Hours, but the columns are not showing up in the calculation.
Any help would be appreciated
Solved! Go to Solution.
Hi, @Sharma0815 , I recommend you create separate dimensional tables for dates and users; then create relationships among all tables, so that you can easily do some calculations. Here's the attached file for more details.
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Productivity Score :=
DIVIDE (
CALCULATE (
SUM ( 'Calls_Handled'[calls_handled] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Calls_Handled[user] )
)
+ CALCULATE (
SUM ( Outbound_Calls[outbound_calls] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Outbound_Calls[user] )
)
+ CALCULATE (
SUM ( Cases_Closed[Cases_closed] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Cases_Closed[user] )
),
SUM ( User_login_Hours[Login Hours] )
)
Productivity Score :=
DIVIDE (
CALCULATE (
SUM ( 'Calls_Handled'[calls_handled] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Calls_Handled[user] )
)
+ CALCULATE (
SUM ( Outbound_Calls[outbound_calls] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Outbound_Calls[user] )
)
+ CALCULATE (
SUM ( Cases_Closed[Cases_closed] ),
TREATAS ( VALUES ( User_login_Hours[user] ), Cases_Closed[user] )
),
SUM ( User_login_Hours[Login Hours] )
)
Hi, @Sharma0815 , I recommend you create separate dimensional tables for dates and users; then create relationships among all tables, so that you can easily do some calculations. Here's the attached file for more details.
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
26 | |
10 | |
10 | |
9 | |
6 |