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 moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hi,
I get my data from an odata feed where the dates come down in UTC plus an offset which includes daylight saving, E.g 21/05/2022 00:00:00 +1 for a date in the UK timezone with daylight saving.
However, all my dates are already in the correct timezone including the daylightsaving. In PBI the dates get changed to include daylight saving which gives incorrect results for the analysis, eg 21/05/2022 00:00:00 +1 is displayed as 20/05/2022.
Ans- syntax-DateTimeZone.RemoveZone(dateTimeZone as nullable datetimezone) as nullable datetime
syntax-DateTimeZone.RemoveZone(dateTimeZone as nullable datetimezone) as nullable datetime
Hi @Macc-PA ,
Not very clear about the situation.
You may try disabling the auto-date-time feature and check again.
If it doesn't work, you may take a look at these topics.
Or share some sample data and expected result here.
Best Regards,
Jay
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 | |
| 9 | |
| 8 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 50 | |
| 27 | |
| 23 | |
| 23 | |
| 22 |