Hi @v-venuppu, thank you for your support and the working hours logic you’ve implemented — it's very helpful.
However, I’d like to clarify the scenario I’m working with:
Let’s say there is an activity that starts on July 9th and ends on July 11th. When I select only July 9th in the date slicer, I would expect to see only the working hours for July 9th — not the total across all days of the activity. Right now, since the activity spans multiple days, it also considers hours from July 10th and 11th, even if I only selected the 9th.
Similarly, if I select only July 11th, I want to see only the hours that correspond to that specific day — not accumulated from the 9th or 10th.
In summary, I’m looking for a solution where:
If a single day is selected, only the hours that fall strictly within that date are counted.
The logic should ignore any overlap from other days of a multi-day activity unless those days are selected as well.
Do you have any suggestions on how I could adjust the measure or filtering logic to achieve this?
Thanks again!
