Forum Discussion
Calculating hours worked
- 3 years ago
Hi Coryanthony
What's happening here is that the calculated column makes a value for $allowed on every single row of data. As there are 3 rows for 7/1/22, naturally there are 3 repeated values of $allowed.
When $Allowed is dropped into a table, it is a number and will be automatically aggregated which is causing those values to Sum.
There are a few things you can do to change this:
1) Change the model so that there is a separate table dimension for employee & date
This will then return just the one value for every combination of the above2) Create a measure that aggregates your existing $allowed column as appropriateIn the UI, create a measure. Here I've just taken a flat averageAllowed_Aggr = AVERAGE(Merge1[$Allowed])You will need to tweak this to sum properly depending on the context that you are going to use. The average above will work for combinations of Employee & Date, but will need changing depending on how you handle totals3) Change $Allocation to a measure rather than a calculated column
This could have performance implications, but the equivalent of your calculation above, as a measure would be:
Allowed_As_Measure =
SumX(SUMMARIZE(
Merge1,
Merge1[Employee ID],Merge1[Date],Merge1[Holiday],Merge1[Day of Week],
"DailyHrs",sum(Merge1[Hours])),
SWITCH(TRUE,
[DailyHrs]>=4 && [DailyHrs]<8 && Merge1[Holiday] = "Yes" ,12,
[DailyHrs]>=8 && Merge1[Holiday] = "Yes" ,32,
[DailyHrs]>=10 &&'Merge1'[Day of Week]<=4,20,
[DailyHrs]>=4 && [DailyHrs]<8 && 'Merge1'[Day of Week]>=5,12,
[DailyHrs]>=8 && 'Merge1'[Day of Week]>=5,32,
0
))In this, I am assuming that the totals need to be summed. I have also replaced the if statements with a switch() - this is a much cleaner way to introduce much logic.In addition to the above, notice how changing to a measure introduces "0" instead of blank.HTHPi
Hi Coryanthony
What's happening here is that the calculated column makes a value for $allowed on every single row of data. As there are 3 rows for 7/1/22, naturally there are 3 repeated values of $allowed.
When $Allowed is dropped into a table, it is a number and will be automatically aggregated which is causing those values to Sum.
There are a few things you can do to change this:
1) Change the model so that there is a separate table dimension for employee & date
3) Change $Allocation to a measure rather than a calculated column
This could have performance implications, but the equivalent of your calculation above, as a measure would be:
Allowed_As_Measure =
SumX(SUMMARIZE(
Merge1,
Merge1[Employee ID],Merge1[Date],Merge1[Holiday],Merge1[Day of Week],
"DailyHrs",sum(Merge1[Hours])),
SWITCH(TRUE,
[DailyHrs]>=4 && [DailyHrs]<8 && Merge1[Holiday] = "Yes" ,12,
[DailyHrs]>=8 && Merge1[Holiday] = "Yes" ,32,
[DailyHrs]>=10 &&'Merge1'[Day of Week]<=4,20,
[DailyHrs]>=4 && [DailyHrs]<8 && 'Merge1'[Day of Week]>=5,12,
[DailyHrs]>=8 && 'Merge1'[Day of Week]>=5,32,
0
))
Hi pi_eye
I love the measure! It is doing exactly what i've spent half of day attemping to figure out.
Follow up question if I may. On days an employee submits >1 expense, on a different report number, it is doubling the allowed amount. Please see snippet. would you happen to have any solution for this? I would like it to only display the allowed amount for that day (not based on amount of reports submitted.
On 11/22/2022, 2 reports were submitted; therefore, it is calculating $20 for both reports, rathan than only $20 for that day.
Additionally, it appears i am getting a blank rather than 0 on days time was not supposed.
Thank you again for your time, much appreciated :).