Unexpected error: Arithmetic operation resulted in an overflow.

[Cleudson_Rego]

Hi! How can I fix this problem: my BI was working very well, but suddenly when I refreshed my report, this error occurred. I searched to see if changing the number type would fix the problem, but in my case I can't access the table to try changing the columns.

Unexpected error: Arithmetic operation resulted in an overflow.
Details:
Microsoft.Mashup.Evaluator.Interface.ErrorException: Arithmetic operation resulted in an overflow.--->

[parry2k · Accepted solution]

@Cleudson_Rego can you use value with quotes

where CD_UNID = 32

[v-tejrama]

Hi @Cleudson_Rego ,

This error typically occurs when numeric fields in your dataset contain values that exceed the limits of the data type used by Power BI. It often happens if a column receives larger numbers than before or if a calculation produces results outside the supported range.

To resolve this, review the column types in Power Query for the affected table and ensure that fields with large or precise numbers are set to Decimal Number or Int64, rather than Whole Number. If you cannot access the table due to query load failure, consider removing or commenting out the last few applied steps in the query editor to allow it to load, then reapply the steps individually to identify where the overflow begins. Once identified, update the column to a more suitable numeric type or use a try otherwise expression to manage invalid or excessively large values.

Additionally, check the query in your source system, such as SQL Server Management Studio, to confirm that no unexpected values are present. After making these adjustments, refresh your report to verify that the error is resolved.

Thank you.

[v-tejrama]

Hi @Cleudson_Rego ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you.

[v-tejrama]

Hi @Cleudson_Rego ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[parry2k · Accepted solution]

@Cleudson_Rego can you also run the same query in SSMS or another way to see that the issue is not with the query itself.

[parry2k · Accepted solution]

@Cleudson_Rego can you use value with quotes

where CD_UNID = 32