Filtering results based on slicer value

[ErPat]

I have a slightly different and weird data configuration.  I have two tables that are structured differently (shown in separate visuals on the same report) and needs to be filtered different using a single slicer as shown below:

Let's say that teams are grouped as follows:

Team A is a team on its own

Team B is composed of three teams as follows:  Team C, D, E

On Table 1, data is given for each team including separate data for Team B (which is composed of C, D and E) (ignore the "Data" column as those are just arbitrary values used for illustration)
Table1

Team Name	Data
A	1
A	2
B	3
C	4
D	5
D	4
E	3
E	2

On Table 2, data is only given for each team but not for Team B as follows:

Table 2

Team Name	Data
A	2
A	3
A	4
C	2
D	3
E	4
E	5

I have a multi-select slicer that lists all Teams A, B, C, D, E.

My question is, if I select Team A, C, D and/or E, I need to display and filter as usual for both tables.  But if I select Team B, I need to display the Team B data (but not Teams C, D, E) from Table 1 and Teams C, D, E from Table 2.  I am guessing I would need a measure for Table 2 but can't figure out how to do it.  Please note that the slicer is also multi-select and there should be no duplication of data.

Basically, the slicer should work normally for Table 2 except when Team B is selected.  It should also account that a multi-select or "Select All" should ignore Team B for Table 2.

I know that the data is weird but I need to work with what I have.

[amitchandak]

@ErPat , Create a new column Table 2 and join that with common team dim, Also join table 1 with common team dim

New Team = Switch(True(),

[Team] in {"C", "D", "E"}, "B",

[Team]

)

Team Dim = distinct(union(Distinct(Table1[Team]), Distinct(Table2[Team])))

[ErPat]

Thanks @amitchandak, I tried that solution earlier but it won't show anything if I select individual Teams, ie, C, D or E.  Also, I forgot to mention that there is another table relationship (Date) linked to both tables which prevents me to link both tables to the Team slicer table (would introduce ambiguity).