Solved: Compound key

brunozanoelo · ‎03-10-2017

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.

Phil_Seamark · ‎03-10-2017

Compound keys are less essential in an Analytics/Reporting environment, but yes if you concatenate the values you can create relationships between tables.

To learn more about DAX visit : aka.ms/practicalDAX

Proud to be a Datanaut!

View solution in original post

Phil_Seamark · ‎03-10-2017

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.

To learn more about DAX visit : aka.ms/practicalDAX

Proud to be a Datanaut!

MaxW · ‎06-21-2018

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

Anonymous · ‎09-17-2017

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??