Forum Discussion
Inaccurate/Incorrect Month Appearing in Filter
Hi guys,
Just had something odd happen. So I recently updated Power BI and noticed that it's done some odd things to my filter by adding an extra "month" labelled 30 September 2017.
My data is originally in text form, "September 2017" but BI converts it into a date when I import the data so it's "1/9/2017". When using a filter, September is split into 1 September 2017 and 30 September 2017 and its the only month to do so. No other months are split like this. I've gone into edit queries and checked the date and there is no 30 September 2017 (only 1/xx/17) in there so I'm not sure what's happening. When I click on the filter and look at any of my other visuals, they're all blank as I'd expect, but why is it there then. There's no data associated with that
Could anyone offer any insight into this?
Cheers
Edit1: Looking at the filter, my option to select October is completely gone. When I put the month into a table, the October data is there!
I've tried editing the data source and reselecting the data to reload it but this has not worked.
Edit2: File from either link: https://ufile.io/tomsa
https://drive.google.com/open?id=1iowO705IDY2vAgDLf3VVF8zJAJjB7hZX
I opened up another Power BI file and found one of my filters looks like the image below but only for October (other months look normal and only have the date not the time/time zone). If I select the filter and click another month, October completely disappears from the filter. This occurs when I update my Power BI every month and open a file made in a previous version.
Thanks for sharing us your sample data. It helps a lot to repro your issue.
Then for this issue, the newer version of Power BI desktop seems like will detect the text value automatically. And if the values are like date data, it will convert to date type automatically. You can verify this by checking at Edit Queries side.
To resolve this issue, you can simply change the data type to text in above power query script in screenshot.
Thanks,
Xi Jin.
17 Replies
I've shared the data file above.
If I create a new report using the file it is fine, but creating the report again is very time consuming so I would rather not do it again
Thanks for sharing us your sample data. It helps a lot to repro your issue.
Then for this issue, the newer version of Power BI desktop seems like will detect the text value automatically. And if the values are like date data, it will convert to date type automatically. You can verify this by checking at Edit Queries side.
To resolve this issue, you can simply change the data type to text in above power query script in screenshot.
Thanks,
Xi Jin.v-xjiin-msft I noticed that this is an option but then the months are not displayed in the correct order which is quite troublesome.
I went ahead and changed to text and then back to date to see if that would work but that was unsuccessful.
Another screen shot below which is what happens when I click on the filter with October displayed incorrectly. October is in there, but if I click another month, October disappears as if PowerBI has realised that data has been updated. October is also at the bottom which is odd as it should be in calendar order.
But it works in my report. Please refer:
Have you applied the changes for your report? Then for the order in the slicer, since the month column is a text column. So the order should be in text order not the calendar order which is like my above screenshot.
Also, it will be more helpful to troubleshoot your issue if you can share us your report file (pbix).
Thanks,
Xi Jin.
Hi Xi Jin,
I am experiencing the same issue since January update. Initially, the issue was limited to Power BI Desktop, so was waiting for it to get sorted by next update. But, I am still experiencing it after March update as well. Moreover, now my clients are also experiencing this issue on Power BI Service, however, everything is good at my end(Power BI Service). I am able to see "October 2017" in my slicers and filters.
Would really appreciate if you could please let me know why we are experiencing this issue and the time line when this will be sorted by Microsoft.
Thanks,
SJ
He is not a dev so probably cannot give you a time window for this to be fixed. I've tried looking on the forum to answers to this question but I was unable to find any information about it.
MS may be unaware of the issue right now so it may not be fixed for some time. It doesn't look like all users are experiencing the same problem we are.
