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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Rice
Helper I
Helper I

DAX Optimization - Business Hours Elapsed Calculated Column

Hello All!

 

I would appreciate your assistance with optimizing a calculated column. The goal is to calculate elapsed business hours between startdate and enddate.

 

Annoyance is that there's a potential for multiple business hour periods per weekday, so turns into a fun little challenge (at least for me).

 

I've put together a demo model for assistance. [Demo Model Download Link] 

 

Please see the calculated column BusinessHoursDurationTest for additional comments.

 

Thanks in advance!

 

Update: Made it slightly more efficient by separating the hours calculation between 1st day, lastday and middledays. Then added conditions to only 1stday and lastday to properly calculate the unique scenarios for each.

1 ACCEPTED SOLUTION
OwenAuger
Super User
Super User

Hi @Rice 

Try this. It runs in well under a second for me in a test query.

 

BusinessHoursDurationTest-Owen =
VAR OneSecond = 1 / 3600 / 24
VAR StartDate =
    'SD - Incident Report Opened'[Date Link - Incident Submit Date]
VAR EndDate =
    'SD - Incident Report Opened'[Date Link - Support Centre Response Date]
VAR StartTime =
    'SD - Incident Report Opened'[Incident Submit Time]
VAR EndTime =
    'SD - Incident Report Opened'[Support Centre Response Time]
VAR StartDateTime = StartDate + StartTime
VAR EndDateTime = EndDate + EndTime
VAR DateRange =
    CALCULATETABLE (
        SELECTCOLUMNS (
            'Date',
            "Date", 'Date'[Date],
            "Weekday Number", 'Date'[Day of Week Sort] + 0
        ),
        DATESBETWEEN ( 'Date'[Date], StartDate, EndDate )
    )
VAR BusinessHoursFiltered =
    -- Customer filter applied by context transition
    CALCULATETABLE (
        SELECTCOLUMNS (
            'Business Hours',
            "Weekday Number", 'Business Hours'[Weekday Number] + 0,
            "Business Hours Start", 'Business Hours'[Business Hours Start],
            "Business Hours End", 'Business Hours'[Business Hours End]
        )
    )
VAR DateBusinessHours =
    NATURALLEFTOUTERJOIN ( DateRange, BusinessHoursFiltered )
VAR BusinessHoursCalculation =
    SUMX (
        DateBusinessHours,
        VAR CurrentBusinessHoursStart = [Date] + [Business Hours Start]
        VAR CurrentBusinessHoursEnd = [Date] + [Business Hours End]
        VAR EffectiveStart =
            MAX ( StartDateTime, CurrentBusinessHoursStart )
        VAR EffectiveEnd =
            MIN ( EndDateTime, CurrentBusinessHoursEnd ) + OneSecond -- Align with original calc based on discrete seconds
        RETURN
            ROUND (
                MAX ( BLANK ( ), EffectiveEnd - EffectiveStart ) * 24,
                3
            )
    )
RETURN
    BusinessHoursCalculation

 

Notes:

  • The basic idea is to determine the StartDateTime and EndDateTime at the start, then determine the portion of each segment of Business Hours that lies within that range.
  • I used NATURALLEFTOUTERJOIN to join DateRange to BusinessHoursFiltered, then iterate over that table.
  • Didn't use 'Ticket Time Table' to count seconds, but rather calculated difference between datetime values.
  • I added a second to the end time to align with your original calculation.

Regards,

Owen

 

 


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
Twitter
LinkedIn

View solution in original post

4 REPLIES 4
OwenAuger
Super User
Super User

Glad to hear it! You're welcome ☺️ 

I'll send you a separate message 🙂


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
Twitter
LinkedIn
Rice
Helper I
Helper I

Thanks for your time and answer, I'll do some validation to confirm, but initial testing proves very promising!

OwenAuger
Super User
Super User

Hi @Rice 

Try this. It runs in well under a second for me in a test query.

 

BusinessHoursDurationTest-Owen =
VAR OneSecond = 1 / 3600 / 24
VAR StartDate =
    'SD - Incident Report Opened'[Date Link - Incident Submit Date]
VAR EndDate =
    'SD - Incident Report Opened'[Date Link - Support Centre Response Date]
VAR StartTime =
    'SD - Incident Report Opened'[Incident Submit Time]
VAR EndTime =
    'SD - Incident Report Opened'[Support Centre Response Time]
VAR StartDateTime = StartDate + StartTime
VAR EndDateTime = EndDate + EndTime
VAR DateRange =
    CALCULATETABLE (
        SELECTCOLUMNS (
            'Date',
            "Date", 'Date'[Date],
            "Weekday Number", 'Date'[Day of Week Sort] + 0
        ),
        DATESBETWEEN ( 'Date'[Date], StartDate, EndDate )
    )
VAR BusinessHoursFiltered =
    -- Customer filter applied by context transition
    CALCULATETABLE (
        SELECTCOLUMNS (
            'Business Hours',
            "Weekday Number", 'Business Hours'[Weekday Number] + 0,
            "Business Hours Start", 'Business Hours'[Business Hours Start],
            "Business Hours End", 'Business Hours'[Business Hours End]
        )
    )
VAR DateBusinessHours =
    NATURALLEFTOUTERJOIN ( DateRange, BusinessHoursFiltered )
VAR BusinessHoursCalculation =
    SUMX (
        DateBusinessHours,
        VAR CurrentBusinessHoursStart = [Date] + [Business Hours Start]
        VAR CurrentBusinessHoursEnd = [Date] + [Business Hours End]
        VAR EffectiveStart =
            MAX ( StartDateTime, CurrentBusinessHoursStart )
        VAR EffectiveEnd =
            MIN ( EndDateTime, CurrentBusinessHoursEnd ) + OneSecond -- Align with original calc based on discrete seconds
        RETURN
            ROUND (
                MAX ( BLANK ( ), EffectiveEnd - EffectiveStart ) * 24,
                3
            )
    )
RETURN
    BusinessHoursCalculation

 

Notes:

  • The basic idea is to determine the StartDateTime and EndDateTime at the start, then determine the portion of each segment of Business Hours that lies within that range.
  • I used NATURALLEFTOUTERJOIN to join DateRange to BusinessHoursFiltered, then iterate over that table.
  • Didn't use 'Ticket Time Table' to count seconds, but rather calculated difference between datetime values.
  • I added a second to the end time to align with your original calculation.

Regards,

Owen

 

 


Owen Auger
Did I answer your question? Mark my post as a solution!
Blog
Twitter
LinkedIn

Finally got around to validating this today. 

 

Exactly what I needed. Thank you for your assistance! 

 

Is there anywhere I can donate a tip to?

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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