Lookupvalue not working between 2 tables

[o59393]

Hi all

I am doing a lookup calcualted column, but doesn't work

Basically I have a table called 'Master Plant & Product' that has to xlooup its values on another table called 'SKU by line - Official'.

The IF statement I use is very simple:

IF value in column Merged Plant & Product of 'Master Plant & Product' table is found in column Merged Plant & Product of 'SKU by line - Official' table, then return an "Exists" else "Doesn't exist".

The example above is explained in this excel: https://1drv.ms/x/s!ApgeWwGTKtFdh2c9PC00KsBrHMrF?e=AMkZgI

I am trying to replicate that with a lookupvalue but gives me an error:

The relationship is a 1:M

Can you please advise how to make it work?

Thanks.

[o59393]

Hi @KNP 

The purpose is to have an alert system when user misses adding the correct data. Long story short I summarized it in that excel to not include all the model and sensible data.

Can we have it in dax calculated column? 

Thanks !!

[KNP]

I think the RELATED function would be more useful given you already have a relationship setup.

Checkout this link.

https://stackoverflow.com/questions/67783229/check-if-value-is-in-another-table-and-add-columns-in-p... 

[o59393]

Hi @KNP 

Look at the error after using related:

Strangely I do have a relationship.

Any idea?

Thanks.

[KNP · Accepted solution]

Try this instead...

IF('Master Plant & Product'[Merged Plant & Product] IN DISTINCT('SKU by line - Official'[Merged Plant & Product]), 1,0)

I may have typo'd your column names so double check those.

[o59393]

Wow @KNP 

It worked! so the distinct in your dax basically converted the duplicated values to unique ones correct?

Thank you so much 🙂

[KNP]

It just gets the unique values of that column from the SKU table to compare with the Master table. So not to compare every row. 

At least, that's how I understand it to work.

Glad I could help, especially since my DAX knowledge is a work in progress. 😁

[o59393]

Thank you so much @KNP 

I guess the duplicate values on the SKU table were making noise and couldn't return the value.

Thanks!

[KNP]

Just did some testing/reading.

Looks like the RELATED (at least in this scenario) only works on the table on the 'many' side of the relationship. So in your case, the column would need to be added to the SKU table I believe.

There will be a better way. Going to do some more investigation.

[KNP]

Can you double check the column name in the SKU table?

It isn't recognising it for some reason.

[KNP]

If you need a DAX solution I'll leave it for someone better versed in DAX.

If you wanted Power Query I'd simply merge with appropiate joins to only keep existing/non-existing.

[KNP]

As far as the report is concerned, what is the purpose of the 'Product Exists' column?

Would you be happy for a Power Query solution or does it need to be DAX?