Forum Discussion
Table Connections
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:
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.
- CoreyP2 years agoSolution Sage
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.