Date slicer is not changing date when selecting other slicer

[manualen]

Hello all,

We're trying to desing a dashboard in which we have 2 slicers:

1) Date slicer with between option

2) Mosaic slicer in which I can select the Department.

The thing is that as you can see, first date od data set is 01/01/2022 but I want that when I select a Department, the date of Date Slicer changes also.

But this doesn't happens and this feature/bug is just present on this kind of slicer. If I try it with other Date Slicer it works.

Do you know if there is any way to perform this but with first slicer showed?

Thans a lot in advance

[manualen · Accepted solution]

Hello all,

Just for your information the solution applied was:

1) Created required slicers
2) Go to Format

3) Selecting Department, enable filter bottom of Date Slicer

Neither any additional tables.

I've checked using bi-directional relationship and it worked. But then i've tried removing this bi-directional relationship and it worked also. I don't know if it worked without bi-directional relationship, but maybe data as it's cached and if data is updated it'll fail.

Anyway, the general solution is proposed one and with bi-directional relationship.

Thanks a lot to everyone for feedback

[lbendlin]

That is a question for your data model, your selected fields, and then search/filter direction.

BTW, your desired behavior is considered sub-optimal for Power BI performance.

[manualen]

Hello @lbendlin,

The thing is that i want that when I select a department, the date on slicer change also without any interaction on this slicer.

I don't understand the reason of this commented sub-optimal performance due to it's that happens in others date slicers. Do you know if this requeriment is possible?

Best Regards

[lbendlin]

It is possible but potentially undesirable. 

Please provide sample data (with sensitive information removed) that covers your issue or question completely, in a usable format (not as a screenshot).
https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
Please show the expected outcome based on the sample data you provided.

https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447...

[manualen]

Hello,

The data is example data just to test it. Anyway you can use this test data to check it.

01/01/2022;IT;30
02/01/2022;Marketing;45
03/01/2022;CEO;42
04/01/2022;Big Data;39
05/01/2022;IT;31
06/01/2022;Marketing;36
07/01/2022;CEO;30
08/01/2022;Big Data;38
09/01/2022;IT;26
10/01/2022;Marketing;50
11/01/2022;CEO;30
12/01/2022;Big Data;41
13/01/2022;IT;28
14/01/2022;Marketing;47
15/01/2022;CEO;28
16/01/2022;Big Data;49
17/01/2022;IT;34
18/01/2022;Marketing;31
19/01/2022;CEO;49

For example if I select CEO in a slicer I want that date in the slicer with Between option be changed from first date that CEO appears on the dataset (03-january-2022) until last date that CEO appears (19-January-2022).

Thanks a lot for your feedback and if you need any other additional information from my end please do not hesitate to request it to me.

[Anonymous]

Power BI is using their own Date table in the backround to set the values for the Slicer, and likely using a max and a min date from your dataset as the starting and ending points. At a high level, I would create a custom date table (find one in PBI community), mark it as your date table in the modeling tab, and then allow the tile filter to filter that date table. In order to avoid data errors, I would split out a seperate table for the distinct categories/date combos (parent data) which will require some Power Query knowledge, and the have it BI directionally cross filter with the date table, that then filters the values table, as I would call it the record table. Make sure the tile filter is set to the field from the categories/date combos table according to the model imaged below. 

Note that, as mentioned by @lbendlin , this is really a bum requirement, and should be avoided unless some client simply can't live without. If your model is more complex, bi-directional filtering like this could cause ambiguous relationships, although I do not think bi-directional is necessarily needed in this case. 

[Anonymous]

The multi table idea was not needed as I reviewed this solution. A simpe bi - directional filter gets the job done... but this will only be effective if you set at the visual level that the date filter cannot effect the Tile filter. Updated model below 

If your data model really is that simple, this should behave "fine", but if you have a lot of data sources and tables being joined relationally, you need to be careful with this. 

[lbendlin]

For example if I select CEO in a slicer I want that date in the slicer with Between option be changed from first date that CEO appears on the dataset (03-january-2022) until last date that CEO appears (19-January-2022).

Please explain why you need that. It will be a lot of work to implement, for no obvious benefit.