How to filter a visual based on non-selected field from another visual

[bottos]

I have only one data source table (Duplicates) for my report. I used a visual (table) that uses the field UserName from the Duplicates table source. Additionally, I have another visual (table) that shows the fields InvoiceID, Amount and PrimaryKey from the Duplicates table source as well.

What I want to accomplish is when I click on the UserName row from the first visual, I want the second visual to show only the rows with the PrimaryKeys associated to the UserName. In other words, I want to filter the second visual based on a non-selected field of the first visual.

It sounds simple, but I am struggling a lot. Any help is greatly appreciated. Thanks.

[muhammad_786_1]

Hy @bottos,

This is a default feature in Power BI. Ensure the interaction between visuals is set up correctly. If this does not address your query, please share some sample data along with your desired output. This will help us provide a more accurate solution.

Best Regards,
Muhammad Yousaf

If this post helps, then please consider "Accept it as the solution" to help the other members find it more quickly.

LinkedIn

[bottos]

Hi @muhammad_786_1 

Thank you for your reply.

This is an example of a dataset:

UserName	InvoiceID	Amount	PrimaryKey
John	1234	100	1234100
John	1234A	100	1234100
Beth	1234E	100	1234100
Beth	4567B	200	4567200
Jack	7890	300	7890300
Jack	7890C	300	7890300

My first visual table looks like this:

UserName

John

Beth

Jack

What I need to do is when I click over 'John', for example, instead of filtering the data by UserName, I need it to be filtered by PrimaryKey, or, the PrimaryKeys that are associated with 'John'.

The expected result would be something like this:

UserName	InvoiceID	PrimaryKey
John	1234	1234100
John	1234A	1234100
Beth	1234E	1234100

Does it make more sense now?

[muhammad_786_1]

Hy @bottos 

Your data structure is not correct. The PrimaryKey column seems to represent unique invoice groups, but multiple UserNames are associated with the same PrimaryKey

Instead of relying on PrimaryKey for filtering, you should normalize your data properly. A separate table linking PrimaryKey to UserName would make filtering logical and efficient.

Best Regards,
Muhammad Yousaf

If this post helps, then please consider "Accept it as the solution" to help the other members find it more quickly.

LinkedIn