Forum Discussion
Incorrect dates displaying in desktop, but web is fine when published
Thank you for your prompt response.
I have oulled the same data source in to a new PBI Project, which only contains the one single data source.
Attached are 3 screen shots.
1. Data Source as per MSSQL
2. PBI Desktop View
3. PBI Web View
I am making no data transformations on the way in to PBI, simply changing the date format. Regardless of the date format, the problem exists.
I have changed the PBI project to be "Direct Query" and "Import" --> Same problem exists.
You will see from attached that the Data source has dates as '2017-10-01'.
When viewed in Desktop - date is displaying incorrectly as '2017-09-30'
and in Web view - date is displaying correctly as '2017-10-01'
Data Source in MSSQL = Date is '2017-10-01'When view in Desktop = Date is '2017-09-30'When view in Web = Date is '2017-10-01'
I have the exact same issue as well at one of our client, just noticed it yesterday. I am using the latest Power BI desktop Version: 2.57.5068.501 64-bit (April 2018)
The 'incorrect' date appears to always be a Sunday and in either week 39 or week 40 depending on the year (might have to do with some years have 52 and others have 53 weeks). See attached imaged (highlighted).
OrmesomeHelper II
Is there any chance the underlying data has a time component that is shifting particular records between days based on timezones?
No, the CalendarDate column is date only, no time whatsoever (or all is 00:00:00), unless.... that's when the Daylight Savings Time kicks in, which it is for some of the more recent years but not for for the old years.
So I brought in the time component, all 00:00:00, and voila, at the date where it's shown wrong, the clock has been winded back 1 hour (from 12:00 AM to 11:00PM) and hence why the date is shown as previous date. And I've used the datetimeoffset for the CalendarDate data type, with UTC timezone (+00:00). If I look at April, sure enough it winds the clock forward 1 hour.
- Ormesome
Does it make a difference whether the field is a Date/Time or a Date? I'm hoping that telling the Data Model that it's a Date will cause it to ignore any time shifting.