Switch Time Zone on DateTime Columns based on User Selection

The safe way to keep timezone and the date slicer aligned is to store all timestamps in UTC, add a “local date” column upstream for each timezone you need, and use that local date column in the slicer while using measures only to show the converted datetime.

You can add additional columns in Power Query that convert your UTC datetime column to the different time zones you want to support, then use a field parameter to let users switch between them based on a slicer selection.

However, keep in mind that datetime columns are highly cardinal and can significantly increase the size of your semantic model. Also, Power BI does not automatically detect and apply daylight saving time adjustments. If you need to support DST, you generally have to build additional logic around timezone rules, including the dates when the offset changes. This can become surprisingly complex because DST rules vary by country and can change over time (such as when the start and end within a given year).

Example timezone conversion

if Value.Is([UTC datetime], type datetimezone) then
    DateTimeZone.RemoveZone(
        DateTimeZone.SwitchZone([UTC datetime], 8)
    )
else
    DateTimeZone.RemoveZone(
        DateTimeZone.SwitchZone(
            DateTime.AddZone([UTC datetime], 0),
            8
        )
    )

Hello SahilKothekar,
There are really two problems hiding in this one: getting the UTC timestamps to show correctly in whatever time zone the user picks (DST included), and making sure the date slicer doesn't drift out of sync once you do that conversion.
For the display part, a disconnected Time Zone table works well. Let the user pick a time zone from the table, then use a measure to adjust the datetime based on their selection. I wouldn't hardcode the offsets though, since DST means the correct offset changes depending on the date. A lookup table is a better option.
The slicer is where people usually get tripped up. Measures can't be used as slicer fields, and calculated columns (including Power Query output) are only evaluated during data refresh, so they won't react to a user's time zone selection at runtime. The slicer can only filter on the stored column values in the model. It can't switch dynamically based on a measure.
Microsoft has a good explanation of the differences between measures, calculated columns and power query:

Use calculation options in Power BI Desktop.
If the business requirement is that the slicer filters by the user's local date, then you'll probably have to rework the model. If the business really needs the slicer to work off the user's local date, then the model will probably need to change.
One option is to precompute local date columns for each supported time zone. Another is to maintain a lookup table that contains the local dates and the DST rules for those time zones.
A couple of questions first:
1. Is the model Import or DirectQuery?
2. Where is the data coming from? SQL Server, Fabric, Azure SQL, Dataverse, or something else?
The answer will depend quite a bit on those details.

Hi SahilKothekar,

Have you had a chance to review the solution shared by Olufemi7 MohamedFowzan1 Kagiyama_yutaka danextian ? If the issue persists, feel free to reply so we can help further.

Thank you.

Hi SahilKothekar,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.