Forum Discussion
Helper IMap not affected by slicer
1. Create a new Calculated Table:
Category = DISTINCT('Grouping'[Category])2. Create a new Calculated Column in your grouping table:
Category Count = 1
3. Add a relationship between the new Category table and the Grouping table.
4. Add the Category Count to the map (size?)
5. Change the Slicer to the new Category table.
Here is the pbix.
Cheers,
Nathan
Hi, you are joining tables 'Grouping' and 'StopPoints_2018' based on the ID fields in both tables, however there are comparably few matches between the values in each of the ID fields. This might be the issue.
Helper IThe number of matches should not affect the overall behaviour - this would be classed as a bug. Even if there was a single category in one of the tables and it only matched 1 entry in the other table this should still work. The fact that clicking on the map filters the category demonstrates that this is working.
In any case, I have updated the data model and only included a small subset of the data. The same behaviour exists.
Updated dashboard, same problem: https://1drv.ms/u/s!Avv4DxzuMuq2kIFBzqEVwHB2mn49mQ?e=HasYEo
The relationship between the 2 tables is such that the Grouping table does not filter the StopPoints table. You will need to modify that relationship.
Hope this helps,
Nathan
- rvcedd
Hello Nathan - can you explain exactly what I need to modify? Currently the relationship is 1 to many - why is this not working and what is the correct solution?
The quickest way to address it would be to set the filter direction to both:
However, that's not considered a best practice. Another possibility is to create a third table. Then, you'd have your new Category dimension table (a distinct list of Categories), your Location dimension table (stays the same), and then a "Factless Fact Table" (stays the same). Each dimension table would filter the fact table in a one-many relationship.
Hope this helps,
Nathan