Forum Discussion
Datetime field in Report View not the same value as in Data View
Today I noticed a difference between the Data View and Report View for 1 specific field value.
I'm working on a dashboard with global date and time values according to Windows and according to www.timeanddate.com.
On March 27, 2017 02:00 local time (according to the Data View), clocks were moved ahead with 1 hour to March 27, 2017 03:00 in Chita (Russia).
However, that very same field in my dashboard displays March 27, 2017 03:00 instead of March 2017, 02:00.
I can't think of any logical explanation why the very same field would display different values.
Yesterday I noticed a similar phenomenon where a datetime value differed between Power Query and the loaded value to Excel.
(It was a datetime somewhere in 2009, so the cause is not the different numbering between 1/1/1900 and 2/28/1900).
Would there be any technical explanation for this strange phenomenon?
Only explanation that I can think of is that the date/time value is being stored in its "raw" state but when rendering that value within a report, the report is factoring in daylight savings time somehow?
Spot on Greg_Deckler !
Due to local time switches (typically Daylight Saving Time), some date/time combinations do not exist.
Such date/time combinations are allowed in Power Query and the Data Model, but in Report View, such combinations are adjusted, both in Power BI Desktop and in Power BI.
This video clearly illustrates the issue.Expecting a "Wad" * when raising an issue, I raised an idea for improvement, expecting lots of votes :robotlol:
* "Works as designed"
4 Replies
Only explanation that I can think of is that the date/time value is being stored in its "raw" state but when rendering that value within a report, the report is factoring in daylight savings time somehow?
Greg_Deckler Good suggestion. That would explain why the difference is exactly a multiple of an hour (1 hour in Power BI Desktop, 2 hours in Excel / Power Query). Otherwise the issue only happens in very rare situations (these are the only 2 I spotted so far).
Anyhow, I'll take your suggestion for further testing and come back once I have more information or questions.
Spot on Greg_Deckler !
Due to local time switches (typically Daylight Saving Time), some date/time combinations do not exist.
Such date/time combinations are allowed in Power Query and the Data Model, but in Report View, such combinations are adjusted, both in Power BI Desktop and in Power BI.
This video clearly illustrates the issue.Expecting a "Wad" * when raising an issue, I raised an idea for improvement, expecting lots of votes :robotlol:
* "Works as designed"