Slicers not working!

[joglidden]

I am attempting to get any slicer to work, and neither the built-in slicer will work, nor the heirarchy slicer. I try to use a column from one table to select items from another table and I get nothing:

And yet, when I swap out 'Finding Title' with 'Finding_ID', it works fine:

This is of course, unacceptable. I can't be using a primary/foreign key for my slicer. I know that my table relationships are solid:

I am dumbfounded that PowerBI can't work this out. Is this just a broken feature, or is there something I am missing? Any help or suggestions would be appreciated.

[Cgull]

Could this be that the properties of the realtionship is only in one direction. 
Properties, cross filter direction,change from single to both.

[joglidden · Accepted solution]

I think I've figured out the problem: slicers are confused as to which key to follow. One would expect that the slicer would just follow the table relationship, but slicer is apparently overthinking it, ignoring the established table relationship, and looking at other keys, getting confused (because more than one possibility exists), and then just returning a blank. In the other records where there is no possibility of confusion, I am getting records returned from the related table.

Oh well. I'll try something else.

[GilbertQ]

Hi @joglidden

Just to confirm your relationships are the right way around?

EG: 1-Many

Regards

Gilbert

[joglidden]

Thanks for the question. Yes, it's correct, one-to-may in the indicated directions. I'm now thinking there is some sort of issue with the data, because some records will render the table-related data, and some will not. I'm thinking to recreate those records and see what happens.

[CheenuSing]

Hi @joglidden

Based on the data model it should work. Can you share the pbix file in one drive to see what went wrong.

Cheers

CheenuSing

[joglidden]

Thank you so much for your offer to help, but I can't reveal any more of this data. I would have to mock it up somehow.