Forum Discussion
Table filtered with data from another table who has a relationship is not working
I have a visual showing the status of tickets (=issues). This comes from one table.
I have another table containing "labels". The tickets can have 0 to X labels.
The relationship between the two tables is therefore '1 to many' : 1 ticket can be linked to 0, 1 or many labels.
I am now filtering my visual to get rid of any ticket who has the label "contractUpdate" in the Labels table.
The filter shows the right amount of tickets in scope: 20 tickets.
However, when I do apply the filter, more than 164 tickets are taken away from the visual, instead of the 20 expected:
If I change the cross filter direction from "both" to "Single" stricly nothing happens when I remove the label or add it.
I am now really puzzled by this result to the point I think it's a bug.
Any thoughts?
Your help will be very much welcomed.
Thanks for reading!
12 Replies
- Bibiano_Geraldo
Super User
Hi,
Did you tried to use slicer to filter to see the result if keep the same?
Hi,
Yes I tried to use a slicer on the label.
Gives exactly the same results.Now I have just noticed one thing: my version of Power BI is largely outdated.
I will ask our support to update it and see if that solves the issue. I have good hope.- Bibiano_Geraldo
Its always good to have Power Bi Updated, but its suppose to work.
Now, what you can do to troubleshoot, its creating a measure to count the Label name where its equal to ContractUpdate, and then add that measure to a card to see what value appear.
the measure should look like this:test = CALCULATE(COUNT([Label Name], FILTER([YOUR_TABLE, [LABEL NAME] = "contractUpdate"))
Thanks. I have used the formula above with COUNTDISTINCT but the formula you just provide gives the same result: 20 values are counted. Not 164+ ...
- Bibiano_Geraldo
Can you share the sample project without sensitive data?
I am afraid not 😞
each row contains something that could be considered as sensitive
It seems to be a problem of blank/multiple possible values.
The filter behaves correctly if and only if:- all ticket KEYS are found in the table "Labels"
- there are only unique tickets KEYS in the table "Labels".
Which is an abnormal behaviour. Is Microsoft Power BI dev team working on this issue?
Anyone knows?
I have seen similar questions on the net for this problem.
