Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
MoYassD
New Member

Table Connections

I have tables with employee names.

 

- Table 1 is a list of cases managed by different employees so each employee has more than one row in the table as they have managed over 20 cases each

- Table 2 is a list of queries each employee has handled, again they appear multiple times they have handle a lot of queries

 

I ideally want to chart from both tables on one tab and use one slicer so all the charts change when I select a name.

 

How can I do this?

5 REPLIES 5
PearlSchneider
New Member

Thanks, I will keep it in my mind.

CoreyP
Solution Sage
Solution Sage

What you need is an employee dimension table. The employee dimension table will have a distinct list of all possible employees in your model. You can create this dimension table in Power Query from your existing tables. 

 

In your Table 1, right click the column header of your employee name field, and select Add as New Query. This creates a new query with all the values of that column in a list. You need to then convert to table:

CoreyP_0-1703224426927.png

 

Repeat these steps for Table 2. You now have 2 additional queries, each with a single column for employee name containing all the values from their source tables. With either of these new queries selected, go to Append Queries > Append as New. This results in a new query with a single column of all the values in Employee Name that occur in both Table 1 and Table 2. This now needs to be a distinct list, so right click the column header and remove duplicates. 

 

Name this new table dim Employees or something. Then you can create a 1:* relationship from this dim table to Table 1 and Table 2. Now you have a proper star schema data model.

@VijayP @Anonymous ,

 

I don't think merging is the proper solution due to cardinality. I also don't think this is a valid use-case for a many to many relationship. Many to many relationships should be avoided whenever possible, and proper star schemas should be created always.

Anonymous
Not applicable

Hi @MoYassD 

Based on your needs, I've created two tables

vjialongymsft_0-1703223998010.png

 

vjialongymsft_1-1703223998012.png

 

 

You can then set the relationship between the employee name fields in the Model View for the two tables

vjialongymsft_2-1703224034479.png

 

vjialongymsft_3-1703224034481.png

 

 

Create a slicer and drag the employe name into the slicer

 

vjialongymsft_4-1703224049090.png

 

 

Then you'll be able to achieve the effect you want

vjialongymsft_5-1703224049091.png

 

 

Best Regards,

Jayleny

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

VijayP
Super User
Super User

@MoYassD  Merge Both tables with required columns which gives you a single Table from there you can achieve the required result




Did I answer your question? Mark my post as a solution! Appreciate your Kudos!!
MY Blog || My YouTube Channel || Connect with me on Linkedin || My Latest Data Story - Ageing Analysis

Proud to be a Super User!


Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors