This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi all,
I have a continious datetime on the x-axis of my line graph which shows datetime in CET timezone. I expllicity set the date format to dd/mm/yyyy hh:nn:ss and this work fine in Power bI resktop as can be seen below.
It shows the correct value: 97.48 for 16/11/2024 01:00:00
However, once I publish it to Power BI service it does not use the 24h clock anymore and it adjuts the datetime to UTC (showing am/pm on the x-axis). But the biggest problem: because of the conversion by Power BI service the value it shows for 16/11/2024 01:00:00 is different! Now it shows that the value is 93.79
I read that Power BI service shows UTC by default but I cant imagine that there is no solution to this.... I don't want to manually shift the hours in Power BI desktop as that can lead to mistakes..
This is very frustating because in the desktop BI works fine so you dont realise of the issue until you publish and it updates automatically as a BI Service. I tried many things and SQL transformations with no success so I worked around creating a CET column in the table view and not in the queries . So the system updates in CET but with a calculated column in the table view it builds the correct date. Here is what I used, sorry for the spanish var names. You can use for your time zone by adding more hours to UCT
date_cet =
VAR Fecha = [date_utc]
VAR Ano = YEAR(Fecha)
VAR lastdaymarch = DATE(Ano, 3, 31)
VAR lastdayoctober = DATE(Ano, 10, 31)
VAR Summertimedate = lastdaymarch - WEEKDAY(lastdaymarch, 1) + 1 //last march sunday
VAR Wintertimedate = lastdayoctober - WEEKDAY(lastdayoctober, 1) + 1 //last October sunday
VAR IsSummerTime = Fecha >= Summertimedate && Fecha < Wintertimedate
VAR Hourdifference = IF(IsSummerTime, 2, 1)
RETURN if(isblank([date_utc]),BLANK(),Fecha + TIME(Hourdifference, 0, 0))
Unforunately no solution has been found yet..
Hi @daircom ,
Based on the description, the method rohit1991 provided should be helpful.
Try to create a column and adjust the time to CET in power query before loading the data to the desktop.
You can view the following document to learn more information.
Solved: Re: Incorrect Time Zone setting at Power BI Servic... - Microsoft Fabric Community
Solved: Converted date resets to UTC after scheduled refre... - Microsoft Fabric Community
Solved: DateTime in Published Report shows as UTC - Microsoft Fabric Community
Best Regards,
Wisdom Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @daircom
Ensure your dataset includes timezone information. If your datetime values are already in CET, confirm this explicitly in your dataset or metadata.
Adjust the timezone in Power Query: Open Power BI Desktop and go to the "Transform Data" option (Power Query Editor). Select your datetime column. Use the "Transform" tab and find the option to convert the datetime to a specific timezone. Set the timezone to CET.
Create a new column in Power Query if necessary: If Power BI Service still displays UTC, create a new column that adjusts the datetime to CET by manually adding the correct offset for your timezone.
Change the regional settings in Power BI Service: Log in to Power BI Service. Go to "Settings" > "Regional Settings". Set the timezone to CET in the regional settings.
Format the datetime in Power BI Desktop: Select the datetime column in your data or visual. Set the format to "dd/mm/yyyy hh:mm" using the formatting options in Power BI Desktop.
Publish the report to Power BI Service again: Save all changes in Power BI Desktop and republish the report.
Verify the datetime values: Check the Power BI Service report to ensure the datetime values remain consistent and are displayed in CET.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 10 | |
| 10 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 27 | |
| 24 | |
| 22 | |
| 21 | |
| 21 |