Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Why i cant use Compound Key in the binding of the tables?
Case:
Company 1 Seller 5
Company 1 Seller 6
Company 2 Seller 5
Should o use one column like "First Pk"_"Second Pk"?
1_5
1_6
2_5
Thanks... waiting for a reply.
Solved! Go to Solution.
Hi @brunozanoelo ,
Compound keys are less essential in an Analytics/Reporting environment, but yes if you concatenate the values you can create relationships between tables.
Hi @brunozanoelo ,
Compound keys are less essential in an Analytics/Reporting environment, but yes if you concatenate the values you can create relationships between tables.
Please be careful concatenating values to create compound keys, ideally convert id's to text and use a separator between them. This is a potential performance hit (text lookups are much slower than integer), but it is often necessary to avoid duplicate keys.
Consider:
Company 1 employee 12 key=112
Company 11 employee 2 key=112
Hey @Phil_Seamark,
I think you need to do some clarification here. On what regards do you claim that compound keys are less essential? Why duplicate data which degrade performance??
| User | Count |
|---|---|
| 49 | |
| 37 | |
| 33 | |
| 22 | |
| 18 |
| User | Count |
|---|---|
| 132 | |
| 99 | |
| 56 | |
| 37 | |
| 37 |