Expression refers to Column object... which has error, but no such reference exists in DAX

[SevsBo]

I have Table 1 with several columns and a "New Column2" that has an error in it, so the results all equate to #ERROR.

I have added a second calculated column with LOOKUP that refers to Table 2 and a column within this table that doesn't have any errors. So the DAX looks something like:

OppName =

LOOKUPVALUE('Table 2'[Name], 'Table 2'[Id], 'Table 1'[Id])

None of these items have errors in them, but when I try to run this I get: This expression referes to a Column object named "New Column2", which has an error.

How is this possible as there is no reference to it in this formula?

[Anonymous]

Hi, @SevsBo 

Welcome to the Power BI forum.
Regarding your question, I noticed that although your expression does not directly include the column New Column2.
However, it states that the column in your expression needs to rely on your error column to run.

You need to check that the red box is not calculated by relying on any other error columns. After my test, if your ID column does not depend on new column2, even if new column2 reports an error, it will not affect the operation of lookupvalue:

If you don't want to remove this erroneous column, you can use the following expression:

OppName = IFERROR(LOOKUPVALUE('Table 2'[Name], 'Table 2'[Id], 'Table 1'[Id]), BLANK())

Best Regards

Jianpeng Li

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[SevsBo]

Apologies for the very belated reply.

I have checked the offending Column that is mentioned but it is entirely self-contained. It does have errors in it but it does not relate to this newly calculated column in any way.
Interestingly, if I delete that whole column, the one with the errors, then I simply get blank results from the new column, even though the data in the lookupvalue should return results.