Date vs. date hierarchy slicer preventing proper filtering?

[RMDNA]

Hi all,

Running into someting weird here. I have some event dates (Start Date) with some attributes (Measure 1 and Count 1). When I filter on Event Date using the "between" slicer at the top, it filters the dates in the left table just fine.

However, when I use in a slicer that's formatted to use the hierarchy on the right, something goes wrong. It filters the middle table of just the dates properly. For the table on the left, it sets the values from the other years as 0, but it doesn't actually filter them out. 

Both slicers are using the exact same field. Is it the presence of the measures? I wouldn't think they'd be able to impact filtering, since they're on the many side of a single-direction 1:many relationship.

I'm trying to figure out how to anonymize this to upload, but it would take a while. Any thoughts?

[fhill · Accepted solution]

Without the data set, or sample data, taking a shot in the dark....

If you remove 'Measure 1' from the table, does it work properly with only 'Count 1' remaining?  (I'm Guessing) the Measure calcuation is still returning Zero (instead of blank or null) when taking your '2018' selection into account.  And those Zeros are still being displayed (as opposed to a Blank or Null that would auto hide?)

Again, just a total guess.  If that doesn't help, try to duplciate the problem with fake data you can share, so we can take a look.  Forrest

[RMDNA]

That worked. Turns out they have to explicitly be BLANK( ) rather than any other option.