Since around monday 10/24/2022, when using a (fixed or FX) datetime value as MIN or MAX of a Graph axis, the value is "shifted" of 1 or 2 hours back (depending on the fact that the datetime selected is in the CET [+1] or CEST [+2] timezone).
It looks as if the datetime was converted from CET/CEST to UTC (subtracting 1/2 hours) and then the new "face value" of the UCT datetime was used as a MIN/MAX value for the x-axis.
The bug appears on the Desktop Client (Version: 2.110.805.0 64-bit (October 2022)) AND on the Power BI Service (patched yesterday 10/26/2022 with the latest version), even on reports that were published on February 2022 and were NEVER refreshed since then: those were correctly rendered at the time, and are now "shifted".
Thanks!
-
KevinChant
on:
Issues with changing the workspace ID when version...
- kdrinnonLex on: BUG: Fabric pipelines stored procedure activity do...
-
JoshT
on:
app.powerbi.com down?
-
DataZoe
on:
Set as landing page feature missing in Apr 2026 up...
-
RossEdwards
on:
Template App "Microsoft 365 Usage Analytics" faili...
- NicoData on: “Filters on all pages” disappear from filter pane ...
- Tortitude on: No able to access Microsoft UI String Search page
- dcullen on: Gateway 3000.314.5 - Microsoft.Mashup.Container.Ne...
-
mattlee
on:
Input Text Slicer Broken on PBI Services
-
mattlee
on:
Input Slicer Bug: Cursor jumps to position 0 and v...