Slicer appears not to be working on table

[Flawn]

Hello All,
I've come across what looks like a bug or some sort of technical issue that I am unable to resolve on my own. I think it is best illustrated via images:

To explain what is shown in the provided screen snips. I have a dropdown slicer that can be used to select for a given date range. While I was noticing this issue using a date table with relationships to the associated table, I wanted to see if the issue still persisted whilst using the native date column (Mcs_bookedon) of the given table. It seems like, for whatever reason - be it with the related date table or with the data-table's own date column - the date slicer is not able to accurately filter for the correct dates. All of the other slicer's for the give table appear to work correctly.

Anybody have any idea as to why this could be happening?

Warm Regards,
Flawn

[v-stephen-msft · Accepted solution]

Hi @Flawn ,

Ritaf1983's insights are great. 

By the way, you could check if the relationship between the tables where your two date columns are located is correct.

I got 2 tables and they have same columns int two tables as an example.

There are two possible scenarios here:

1.There's no relationship between them.

In my table visual, I had a measure to connect two tables. However, there is no definite relationship between the two tables, so it becomes a Cartesian product expansion.

2.Maybe your relationship is not connected to a date column, but to two other fields connected to two tables.

For example, I'm connecting the index column instead of the date column.

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Ritaf1983]

Hi @Flawn 

It seems that there’s a mismatch between the data types of the column in the calendar table. In the column you placed in the table, the data type is Date/Time, while in the slicer, it’s probably just Date.

That’s why the relationship between them isn’t working as expected. To confirm this, you can place both columns in one table and check that they don’t match.

If it is something else 

Please provide a workable sample data and your expected result from that. It is hard to figure out what you want to achieve from the description alone.  

https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[Flawn]

Hi Rita,

Both the column from the table, and the filter are the exact same column, so placing them in the same table wouldn't achieve a great deal. Because they are the exact same column, they also couldn't possibly be suffering from a date type mismatch - they are the same column.

To give you an idea of how strange this is - if both the date field and the date hierarchy from the same date column are included in the same table they do not match with eachother:

Both columns are from the 'bookedon' date field, one is just the hierarchy.

I'll try to generate a working datasample but unfortunately this dataset is filled with data that cannot be shared publically, so cleaning away the identifiable and confidential information may take a while. It's why my screencaps are so oddly shaped as well.

Warm Regards,
Flawn

I'm trying to generate

[Ritaf1983]

Hi @Flawn 

t can also be seen in your screenshot that something is not right. The date and time column shows the year 2019, while in the "Year" column, it's 2024, the month is wrong too...

This is not a bug—the issue lies with something not being properly built in your model.

Are you importing data via Direct Query?
Why do you have the same date and time column in two different tables?
Unfortunately, it's very hard to guess what's not working without access to the file and without knowing exactly what you're trying to accomplish—it's roughly equivalent to trying to give a medical diagnosis without seeing the patient. Everything is just a guess.