Performance of Lookupvalue and Alternatives

[AyubSherif]

I have a Master Data table and a Key table, and I need to look up 13 columns from the master data in the key table.

Master Data:

ProjectID	Value1	Value2	Value3
1	A	C	A
2	B	B	C

Key Table:

Value	Score
A	100
B	90
C	80

I have the two tables separate and created a measure for each column I need to look up:

Value1_Lookup = LOOKUPVALUE('Key Table'[Score],'Key Table'[Value],SELECTEDVALUE('Master Data'[value 1]))

But I am concerned about performance. Is there a better way to do this? I tried the same measure with a Switch function instead of  lookupvalue, but the performance is not much better. Does creating calculated columns into my Master Data a better option here?

Notes, my key table only has 5 values

[Greg_Deckler · Accepted solution]

@AyubSherif Perhaps do a Merge query step in Power Query?

[TomasAndersson · Accepted solution]

Hi!

You can read more about LOOKUPVALUE() and some performance considerations with alternatives here: https://dax.guide/lookupvalue/

Calculated columns are quick as they are calculated on beforehand, when the model is loaded. For the same reason however the model also becomes bigger with calculated columns, so it depends on where your main concerns are. 

[Greg_Deckler · Accepted solution]

@AyubSherif Perhaps do a Merge query step in Power Query?