Power BI to Report builder conversion issues

Hi @John Bazenas

If the calculation is correct in Power BI but returns NULL in Report Builder, first check whether the NULL comes from the dataset query or only from the report expression.

In Report Builder, open Dataset Properties → Query Designer and run the query directly. If the calculation is already null there, compare that DAX query with the query generated by the working Power BI visual. Using the Power BI query with Report Builder datasets, differences in filters/parameters can change a measure's evaluation context.

If the value is correct in the dataset but becomes null only in the report, check the textbox/tablix expression, grouping, filters, and aggregation scope. Report Builder also distinguishes between null and blank values, and aggregate functions such as Sum and Avg ignore nulls.

As a quick diagnostic, you can display the raw field:

=Fields!YourCalculation.Value

and then test explicitly for null:

If this is a DAX measure, also check whether the Report Builder query is supplying the same filters/parameters used by the Power BI visual. A measure can legitimately return BLANK() when evaluated under a different filter context.

Don’t replace the null with 0 yet using COALESCE or an IIF expression, because that can hide the underlying problem instead of explaining why the two reports differ.

If you can share the DAX calculation/measure, the Report Builder dataset query, and whether the value is already null when you run Query Designer, we should be able to narrow down where the difference is occurring.

References:

Create a Power BI Report Builder dataset from a semantic model

Work with nulls and blanks in Power BI Report Builder

Define DAX query parameters in Report Builder

Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.