How to convert datetimes in UTC to Local Time in Power BI?

Question

I have an HR attendance dataset with UTC timestamps, but I need to display local times in my Power BI reports. How can I convert UTC to local time for accurate reporting across different time zones? Is there a way to handle daylight saving time changes automatically?

Introduction

Power BI offers robust solutions to handle this conversion, including automatic adjustments for daylight saving time. Let’s explore how to implement this using a single-table approach.

Assumed Data Model

We’ll define a table named EmployeeActivities. The table will contain the following columns:
Columns: EmployeeID, ActivityTimestamp UTC, ActivityType, TimeZone

Step-by-step Implementation

1. In Power BI, we will use the Modeling tab to create a new measure for local time conversion, using the following DAX:

Local Time = 
VAR CurrentTimezone = SELECTEDVALUE(EmployeeActivities[TimeZone], "UTC")
RETURN
    SWITCH(
        CurrentTimezone,
        "EST", EmployeeActivities[ActivityTimestampUTC] - TIME(5,0,0),
        "PST", EmployeeActivities[ActivityTimestampUTC] - TIME(8,0,0),
        "UTC", EmployeeActivities[ActivityTimestampUTC]
    )

2. The we can also create a calculated column for a more permanent solution:

Local Time Column = 
VAR CurrentTimezone = EmployeeActivities[TimeZone]
RETURN
    SWITCH(
        CurrentTimezone,
        "EST", EmployeeActivities[ActivityTimestampUTC] - TIME(5,0,0),
        "PST", EmployeeActivities[ActivityTimestampUTC] - TIME(8,0,0),
        EmployeeActivities[ActivityTimestampUTC]
    )

3. For automatic daylight saving time handling, use the following DAX formula:

Local Time with DST = 
VAR CurrentTimezone = SELECTEDVALUE(EmployeeActivities[TimeZone], "UTC")
RETURN
    SWITCH(
        CurrentTimezone,
        "EST", DATEADD(EmployeeActivities[ActivityTimestampUTC], -5, HOUR),
        "PST", DATEADD(EmployeeActivities[ActivityTimestampUTC], -8, HOUR),
        EmployeeActivities[ActivityTimestampUTC]
    )

4. Create a time-based visual (e.g., a line chart) using the “Local Time with DST” measure.
5. Add a slicer for the TimeZone column to allow users to switch between different time zones.

Key Concepts

• The SWITCH function allows for different time zone conversions.
• SELECTEDVALUE handles default cases when no specific time zone is selected.
• DATEADD automatically adjusts for daylight saving time, eliminating manual updates.

Make UTC conversion explicit and refresh-consistent

Treat this task as a small diagnostic decision so each result identifies the next useful action. Choose Power Query for refresh-time conversion or DAX for report-context needs. Write down the account, client or device, and exact symptom so that later tests use the same conditions. Change one variable at a time; several simultaneous fixes can hide the real cause and make the problem return.

Protect the current state

Test daylight-saving transitions and users in more than one region. Repeat the test with a simple sample that contains no confidential or business-critical data. If the sample works, compare permissions, file location, policy, and content with the failing case instead of reinstalling the whole product.

Keep the original UTC field for auditing and future recalculation. Keep the original configuration or data until the new result has been checked. When a setting is unavailable, grayed out, or labeled as organization-managed, capture that message and ask the responsible administrator to review the policy.

Know when the issue needs an administrator

undefined. Confirm the result after closing and reopening the relevant app, then repeat it from the normal user workflow rather than only from an administrator or owner account. A successful one-time test is not enough when synchronization, scheduled refresh, or another device is involved.

If behavior differs across clients, record the app version, account type, time of the test, and where the expected result appears. Use that evidence to decide whether the remaining fault is local, account-specific, data-specific, or service-side. This keeps troubleshooting narrow and protects working settings while support investigates the correct layer.

Finally, explain the intended outcome to another user and have that person repeat the shortest safe test. Their result can reveal hidden owner privileges, cached state, or assumptions about where data is stored. Preserve screenshots of error messages only after removing names, addresses, document content, and other private information.

Troubleshooting

• Common issues include incorrect time zone assignments and unexpected results during DST transitions.
• Ensure your time zone column is correctly populated and consider using a date table for more complex scenarios.
• If you encounter discrepancies, double-check your UTC data source for accuracy.
• For multi-time zone reports, remember to clearly label which time zone is being displayed to avoid confusion.