Forum Discussion
April fools?
Hi Philthy,
Are you sure there existing any data record on 1 April 2018 this specific day? You said, the bar chart shows volumes by quarter (so April 2018, Jan 2018, Oct 2017, etc.), it might show the values in a period, we cannot determine there existing data on any specific date.
Regards,
Yuliana Gu
Thanks for the response Yuliana.
Yes - there is plenty of data in there for that date. A simple SQL count by date against the source table (and it's a single table driving the dashboard, so no complexities around table joins to consider) shows tens of thousands of records.
As you'll be aware, when you include a filter in the filter panel, using "basic filtering", the number of records shows up next to each available selection. Curiously, the correct number of records is displayed in this list, but selecting the April quarter blanks out every visualization! But, if I very simply replace the filter with my new text-based version of the date, it works beautifully.
It's inexplicable, and I have absolutely no clue if anyone is able to reproduce it. Unfortunately, it's not easy for me to share the dash to demonstrate, as it contains sensitive data.
I can confirm that we are also experiencing this issue.
I have noted that the issue seems to affect Slicers that are set to April 1st.
Not all kinds of date slicers seem to suffer the issue, however. I have noted that Dropdown and List do have the issue. Other types do not.
Notably, I do not experience the problem with setting the date by the Advanced Filter, but the Basic Filter displays nothing.
I am having the same problem, across multiple reports. I use week ending dates for most of my reports. And the last week ended on 1 April 2018. I can see the date in the data. And I can see the date in reports. But, if I try to filter (using a slicers) for that week - no data appears.
I also have data changing itself. A "End of Hour" (that matches a hour, and a date in other columns) is correct when viewed in Data, but adds a hour itself when viewed in Report.View in dataView in report
Well I'm pleased it isn't just me (though I'm sorry it's affecting you guys too!).
My reports are currently sourced from a single master table, which combines a myriad of stuff into an easily consumed data feed, so all I've done is add an extra field to the ETL process which delivers a text-based date instead of an "actual" date. This works fine (a bit of a pain to have to replace everywhere, but didn't take too long). A bonus to this method is not having to follow the PowerBI date types, so I can format the date however I like (e.g. something nice and short which doesn't take up lots of space).