Forum Discussion
Table Visualization not filtering as expected
- 8 years ago
While I still don't understand the filtering behavior I previously described, I just introduced myself to "Merge Queries" in the Power Query Editor. Performing a "Merge Queries as New" with a left outer join (Table A is the left table), I end up with a merged table where I can set a visual level filter of "'Merge1'[Table B.GUID] is blank" and I'm left with the 90 GUIDs from Table A that don't have a match in Table B.
Understanding the filtering behavior I originally posted about would be great (maybe it's just a misunderstanding on my part), but the "Merge Queries" functionality seems to be a nice alternative to what I was initially trying to do.
While I still don't understand the filtering behavior I previously described, I just introduced myself to "Merge Queries" in the Power Query Editor. Performing a "Merge Queries as New" with a left outer join (Table A is the left table), I end up with a merged table where I can set a visual level filter of "'Merge1'[Table B.GUID] is blank" and I'm left with the 90 GUIDs from Table A that don't have a match in Table B.
Understanding the filtering behavior I originally posted about would be great (maybe it's just a misunderstanding on my part), but the "Merge Queries" functionality seems to be a nice alternative to what I was initially trying to do.
Is there any updates on this? I am experiencing the same situation. I can't share the file unfortunately because of privacy issues.
I have use the same technique on another report and it was working but all the data was coming from the same query. So is it possible that it only works if everything is from the same query?
The expected behavious is not clear.