Forum Discussion
Slicer vs Table Behaviour - different availability of dates
Hi Anonymous ,
Be aware that the slicer altough is a visualization has any other works in a different way than a chart or a table, certain filterings cannot be applied to the slicer and also depending on the type of data you place on the slicer you can have different results.
In the case of date be aware, that Power BI, can be using the auto-date time feature meaning that all date columns will be "changed to a calendar" meaning showing all dates from the frist on your model to the last one.
Can you check if on your file you have the auto date-time turn on?
Thanks for the reply MFelix ,
If that was true (and changing the filter direction to one-way does solve a different issue I had in the report), it'd be true for both the slicer and the table surely? As it is, the bi-directional relationship seems to be affecting the table but not the slicer, or the slicer would only show up to 13/12/21 as well. My confusion is about why the slicer isn't behaving the same as the table, as if the slicer can ignore the relationship in the model and call on the full range of dates. If I change the slicer visual to a table or card, it then only shows dates up to the 13/12/21. Changing it back to a slicer adds in more dates. Is as if there's hidden behaviour in the slicer.
Any ideas?
I'll try mock up and upload a model all the same.
Super UserHi Anonymous ,
Be aware that the slicer altough is a visualization has any other works in a different way than a chart or a table, certain filterings cannot be applied to the slicer and also depending on the type of data you place on the slicer you can have different results.
In the case of date be aware, that Power BI, can be using the auto-date time feature meaning that all date columns will be "changed to a calendar" meaning showing all dates from the frist on your model to the last one.
Can you check if on your file you have the auto date-time turn on?