Forum Discussion
April fools?
We are experiencing the issue too. I have raised a support ticket with Microsoft. My colleague and I worked out that the issue does seem to be related to daylight saving time. I am curious as to whether all of you in this thread reside in countries who have changed their time on either Mar-31 or Apr-1. We're in New Zealand so for us Daylight Saving ended at 3am on Apr-1 with our clocks going back to 2am.
If we have dates in our PBIX file (and the same in the service), when we format them as dateTime, there is obviously not a time component, but if you format that variable as datetime it shows the time as 12:00:00 AM. That is except for on April 1st, where it shows 1:00:00 AM for the time. I believe that this is what is causing the slicers that are built on dates not to work. And likewise the cross-highlighting as Philthy explains.
I have created this very basic report to demo the issue:
On page 1, there is a table and a slicer containing the same date variable. If you select nothing on the slicer, then all three dates show in the table. And if you select Mar 31 or Apr 2, the table is appropriately filtered to these dates. But if you click Apr 1 in the slicer the table shows no data.
On page 2, I've shown the same table but this time with the date formated as datetime (remember I didn't enter those times, I only entered dates, so this is what Power BI is automatically calculating). You can see that Apr 1 has a different time to the other two dates which I am sure must be related to the cause of this problem.
I will update here when I receive action on my support ticket - if the moderators don't do so first.
Update to report a workaround, of sorts. Microsoft support advised that changing your clock settings so that "automatically adjust for daylight savings time" is turned OFF will cause the report to work properly. I have tested this and in my case this is true. Maybe it will be for you guys as well. I've also stated that I don't consider this a solution as asking report consumers to fiddle with the clock settings is not a great option. Will keep this post updated as I hear more.
Thanks, this worked for me. Turned it to "OFF" ran my report, exported the results, and re-imported. Not ideal, but at least I can carry on with other reports.
Thanks but I agree with you it's not an ideal solution becaue we cannot ask all the report consumers to go and off the Day light saving.
Appreciate if you can share us again once you get any resolution to this issue from Microsoft.
Hi Did you hear back from Support team?
Did the support team come back to this issue?
Just confirming the same problem here, and that disabling "Adjust for daylight saving time automatically" in Windows works. For the record, October 2017 data is also affected (the other time of year that daylight saving time starts and ends). This only seems to apply to the Power BI desktop application, as these reports render correctly on Power BI Report Server.
Support team said that the issue in the Power BI service would be fixed in early May. As far as I can tell that did happen. I haven't experienced the issue in the desktop.
We're using the Report Server version, so we haven't had any updates since March. Microsoft, will there be bug fix patches for the Report Server version of the Power BI desktop client?
