Forum Discussion
Expression.Error: We cannot convert the value null to type Number. mysteriously appeared
OK, I finally managed to solve this issue. Error message was in the end misleading.
The error "Expression.Error: We cannot convert the value null to type Number" happened already in earlier steps. For some reason it got expanded to all the columns at the later steps.
The root cause was unexpected values in the code list merged in earlier steps.
OK, I finally managed to solve this issue. Error message was in the end misleading.
The error "Expression.Error: We cannot convert the value null to type Number" happened already in earlier steps. For some reason it got expanded to all the columns at the later steps.
The root cause was unexpected values in the code list merged in earlier steps.
HOW DID YOU SOLVE THE PROBLEM. I'M IN TROUBLE WITH THE EXACT SAME PROBLEM. HELP ME~
Check each step for errors, it may be your data source. I had this error with a query that referenced another query (query A is the referenced query, query B is the query showing the error). Query A has a conditional column I added, but the data source was missing data in the column targeted by the conditional column. Query A loaded but with errors. Query B references A, but won't load because the errors in the conditional column don't permit query B to download the data. I fixed query A, and this cleared the error in query B.
Hello,
I would recommend to follow RobertP22's advice. If I remember correctly, the error happened in completely different columns which I was then processing at the later stages. There was nothing wrong in the column which I was processing at the later stages, but for some reason the error was raised by PQ there. Hopefully you get it solved!
BR,
Jani
Hi,
Please validate if you have any measure with null values in your model. If yes, try to replace the null per 0 or filter it out.
It can be a possible solution to this error.
Regards,
