(Yet another) “Visual Has Exceeded The Available Resources” Error

Hi iW1DOV ,

Thank you for the update.

Since both the visual filter and the “visible measure” method still result in the resource exceeded error, this shows that the problem isn’t with the filter itself. The engine is processing the KPI at a highly detailed level, which leads to a large intermediate result and exceeds available memory, even with a basic condition like > 0.01.

To prevent this row-level recalculation, the most effective workaround is to move the threshold logic outside of the measure.

Recommended Options

1. Create a Visibility Flag in the model
   Add a column upstream (Power Query/Dataflow) like:
   VisibilityFlag = if [KPI] < 0.01 then 0 else 1
   Then, filter the visual using this flag to avoid costly measure-based filtering.
2. Pre-round the KPI column
   If near-zero floating values aren't significant, round them during data preparation. This prevents unrounded values from causing heavy computations when filtering.
3. Check measure complexity
   If the KPI uses iterators (SUMX/FILTER on large tables), consider moving some calculations into the model or using pre-aggregated tables to lower memory usage.

If you can provide a simplified version of the KPI measure, we can help identify what’s causing the resource usage and suggest a more efficient version.

Thank you.