Hi @prantika_sinha, thank you for coming back to me on this.
I have tried your suggestion, but this leaves me with a Custom Aggregate and the same predicament.
I have managed to combine the two, by changing the EndOfMonthFlag from an Average to Custom Aggregate, allowing me to combine this with the Missing Hours (Custom Aggregate):
This still leaves me with the problem that a Threshold Alert cannot be setup on a Custom Aggregate field.
I think I need to take the opposite approach and make Missing Hours an Average Aggregate,
So I can use this with End Of Month Flag, to create an Average Aggregated Combined Flag, which will allow a Threshold Alert. However, I can’t seem to find a way to do this.
Combined Flag - Missing Hours & End Of Month (Custom Aggregate)
ifelse(
{End Of Month Check Avg} > 0
AND
{Missing Hours} > 0,
1,
0
)
Missing Hours (Custom Aggregate)
ifelse(
sum({Timesheet Hours Current Month}) < avg({Expected Hours}),
1,
0
)
Expected Hours (Average Aggregate- Must be Average to work)
netWorkDays(truncDate(‘MM’, ${DateToday}), ${DateToday}) * 7.5
Timesheet Hours Current Month (Sum Aggregate)
ifelse(
substring({timesheet_dated_on}, 1, 7) = substring(toString(${DateToday}), 1, 7)
AND substring({timesheet_dated_on}, 9, 2) <= substring(toString(${DateToday}), 9, 2),
parseDecimal({timesheet_hours}),
0
)
Is there another way I can create a Threshold Alert using a Custom Aggregate field? This restriction seems unnecessarily obstructive.