Slicer not applying to all visuals

[aasamassa]

I have made a dashboard for operational KPI's with a slicer for the different production lines but it applies only to one of the visuals (quality).  You can see in this snapshot, I have selected the line PL2 but for the safety visuals for example, it is displaying 34 incidents, which is the sum for all the lines and not only Line2.

I have added the table view which shopws what the visual is supposed to display and also the model view.  I wanted to add a separate table for the lines and then link it to the other tables but it gives an error as the calendar is the central table. Linking the existing tables through the column 'Line' also doesn't work.

[AlexisOlson]

The first thing I'd check is that the slicer is set to interact with the Safety visual. Make sure the cross-filtering hasn't been disabled via Format > Edit Interactions.
https://learn.microsoft.com/en-us/power-bi/create-reports/service-reports-visual-interactions

[aasamassa · Accepted solution]

Thanks, I checked it and it was already set to interact with the visual.

I think the issue was with the data model. The slicer was using the column 'line' from the table 'quality' and as the cross-filtering was set to 'both' for the all the tables in the model view, I thought that it would've affected the other visuals. 

I modified the model and added a table 'Lines' that i linked to the other tables with the cross-filtering direction set to 'single' and now it seems like it is working.

Apart from adding an extra table, is there any other way to make the slicer affect all the visuals?

Here is a sample of the data I am using

Safety:

Date	Line	Near Miss	Incidents	Safety Habits
2023-12-04	PL2	0	3	2
2023-12-04	PL3	0	4	0
2023-12-04	PL4	1	0	2
2023-12-04	PL5	1	4	5
2023-12-04	PL6	4	0	4
2023-12-04	PL7	4	3	2

Quality:

Date	Line	Number of defects	Number of rework
2023-12-04	PL2	4	1
2023-12-04	PL3	5	0
2023-12-04	PL4	5	3
2023-12-04	PL5	0	2

[AlexisOlson]

If you want to have Line as a slicer that automatically filters each of the tables People, Safety, Quality, and Inventory, then creating these relationships is likely the best solution. Other methods are possible but more work and less computationally efficient.

[aasamassa]

Perfect thanks!