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 moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. 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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 48 | |
| 34 | |
| 27 | |
| 21 | |
| 20 |