1 Slicer to filter multiple visuals at different columns

[Gangula]

I have a project management dashboard in which I have data which says who is a member for the project and who is the respective lead. There are scenario's where a lead for a particular project can be a member of another project. 

Sample data below:

Data_Query

Project	Member	Lead
Project A	Member 1	Member A
Project A	Member 2	Member A
Project A	Member 3	Member A
Project B	Member A	Member 1
Project B	Member 2	Member 1
Project B	Member 1	Member 1

Now I created 2 Table visuals using this which are the same as above. And I want to create a slicer which should filter both. But if I choose Member A in the slicer, it should filter the Lead column in Table 1 and the Member column in Table 2.

Slicer: "Member A"

Table 1:

User as Lead
Project	Member	Lead
Project A	Member 1	Member A
Project A	Member 2	Member A
Project A	Member 3	Member A

Table 2:

User as Member
Project	Member	Lead
Project B	Member A	Member 1

Consider Table 1 & Table 2 as 2 different visuals. Now I want one single slicer to filter Member A in Table 1 from the Member column and the same slicer to filter Member A from the Lead Column.

Is this possible?

[v-piga-msft]

Hi @Gangula ,

I still have a little confused about your scenario.

Which column do you want to use as a slicer in your data sample?

In addition, are the two tables you shared the the results you want after filtering by Member A?

Best  Regards,

Cherry

[Gangula]

@v-piga-msft , yeah the two tables are the results I want after filtering by Member A.

Consider Table 1 & Table 2 as 2 different visuals. Now I want one single slicer to filter Member A in Table 1 from the Member column and the same slicer to filter Member A from the Lead Column.

Currently, the only way that I can think of is to join/append the Lead and the Member columns from Data_Query in a different Query (People_Name) and create a relationship between Data_Query and People_Name and then use the column in the People_Name query in the Slicer.

But this might require some advanced query editing. So I was looking for a simpler solution.