Forum Discussion
composite primary key
Hi GiangLe,
As you know, in Power BI you need a single column to link two tables (you can't define a key with two columns as you can in common databases). This column has necessarily to have unique values on one side of the relationship because Power BI doesn't work directly with a "many to many" relationship. In conclusion, you will need to create a key using two columns with CONCATENATE or create a table with unique values between tables with non-unique values.
Example: You have two fact tables with the sales of your employees and other with the wages of them, both have two columns with the name and surname of the employees. Firstly, you can define a primary key concatenate their name and surname and secondly, you need two create a table between them with the unique values of each employee. In that way, you will have a many (sales table) to one (employee table) relationship and a one (employee table) to many (wages table) relationship and PowerBI will work perfectly.
Hi GiangLe,
As you know, in Power BI you need a single column to link two tables (you can't define a key with two columns as you can in common databases). This column has necessarily to have unique values on one side of the relationship because Power BI doesn't work directly with a "many to many" relationship. In conclusion, you will need to create a key using two columns with CONCATENATE or create a table with unique values between tables with non-unique values.
Example: You have two fact tables with the sales of your employees and other with the wages of them, both have two columns with the name and surname of the employees. Firstly, you can define a primary key concatenate their name and surname and secondly, you need two create a table between them with the unique values of each employee. In that way, you will have a many (sales table) to one (employee table) relationship and a one (employee table) to many (wages table) relationship and PowerBI will work perfectly.