Forum Discussion
Helper IError on Service - Works on Desktop - We're sorry, an error occurred during evaluation
Hi Pawel_1990 , Thank you for reaching out to the Microsoft Community Forum.
Microsoft recently introduced stricter runtime evaluation for DirectQuery sources like Snowflake. Visuals now fail when nulls or unexpected structures are returned at runtime, issues that were previously handled silently.
Your reports haven’t changed, but Power BI Service has. If Snowflake returns a null, an empty join, or altered structure, measures like COUNT([Column]) can now throw errors, while others like DISTINCTCOUNT may still work. To avoid this, wrap measures to handle nulls explicitly.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Community SupportHi Pawel_1990 , Thank you for reaching out to the Microsoft Community Forum.
Microsoft recently introduced stricter runtime evaluation for DirectQuery sources like Snowflake. Visuals now fail when nulls or unexpected structures are returned at runtime, issues that were previously handled silently.
Your reports haven’t changed, but Power BI Service has. If Snowflake returns a null, an empty join, or altered structure, measures like COUNT([Column]) can now throw errors, while others like DISTINCTCOUNT may still work. To avoid this, wrap measures to handle nulls explicitly.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Helper IThis comment helped me to find solution. There are two options:
- rewrite DAX code / Power Query steps to be clean. Check some data types (they like to get messed up in my case)
- other way is to switch [implementation =2.0] at Power Query code level to =1.0 or remove it (it may also mess some data types so check it as well)