Forum Discussion

Gianluigi's avatar
Gianluigi
Helper II
5 months ago
Solved

export from visual table

Hello, I've noticed that when I export a visual table to a CSV file and then import the CSV into Excel, the totals differ slightly. It happens when the number of rows in the visual table is very ...
  • cengizhanarslan's avatar
    5 months ago

    Power BI visuals often show formatted values (e.g., 2 decimals), but calculations use the full precision value.

    When exporting:

    • CSV may contain more decimal precision than shown

    • Excel recalculates totals using raw numbers

    • Result → small differences in totals

    Best practice to fix is to use same decimal number for both the measure and used field values used within it.

  • MohdZaid_'s avatar
    MohdZaid_
    5 months ago

    Hey Gianluigi  , 

     

    Most commonly, this happens because of rounding. Power BI calculates using full precision in the background, even if the visual shows only two decimal places. When you export to CSV, the full precision values are exported, and Excel recalculates the total using those exact numbers. With a large number of rows, small decimal differences can add up.

     

    If that’s the case, you can fix it by rounding the value directly in your DAX measure so both the visual and the export use the same precision.

     

    Another common reason is when the column is a measure (like an average, ratio, or DISTINCTCOUNT). In those cases, Power BI recalculates the total instead of summing the visible rows. So when you sum the exported rows in Excel, it may not match and that’s expected behavior.

     

    So it’s not a bug, but depending on the scenario, it can usually be controlled with rounding or by understanding how the measure total is calculated.