COALESCE  issue in Power BI

Hi Anonymous 

You're facing an issue in your Power BI report where replacing null values in your measures with zeros using the COALESCE function is unintentionally altering the report’s filtering behavior. Initially, when the measure contains null values, the report correctly respects slicer selections (like filtering DIM_DAY[Calendar Date] to 2024), and only relevant data appears. However, after applying COALESCE([Measure], 0), the report starts returning rows for all dates from the DIM_DAY table, not just those related to filtered fact data. This happens because when nulls are left untouched, rows without matching data in the fact table are naturally excluded from visuals (as their measure returns blank). But when you use COALESCE, you’re effectively forcing those unmatched dimension rows (which originally had no fact data) to be included with a value of zero, making them visible in the visuals. As a result, your report now includes extra rows from the dimension table with zero values, inflating the row count and cluttering the view, even though the total value remains accurate. To fix this, you can wrap the measure logic inside a HASONEVALUE or use IF(HASONEVALUE(DIM_DAY[Calendar Date]), COALESCE([Measure], 0), BLANK()) to suppress display of irrelevant zero rows based on context, or explicitly filter out unrelated rows using ISFILTERED or ISINSCOPE combined with FILTER() logic in your DAX to ensure only meaningful combinations appear.