Large (64-bit) integers being displayed as rounded to the nearest 1000th

[ArvindSh-MSFT]

I have a table with large 64-bit integer (whole number) values, like the below:

In the Table view, they are correctly displayed down to the correct value in the least significant 4 digits on the right. So the data is there correctly.

However when viewed in any visual, they magically get "rounded" to the nearest 1000th:

I have tested this with 3 different sources for the data: SQL Server, Azure Data Explorer (Kusto), and even entering data directly into a new table. The "rounding" effect is seen even in slicers and filters where this column is used. It applies equally to positive and negative integers. The data type is confirmed to be Int64 i.e. Whole Number:

Any explanations for this? Thank you in advance for your time and help!

p.s. this is easy to reproduce on a new blank report, by entering data as below:

-2370973230469259890
-3733934645270991410
-2532830190207062677
-2397055034180776732
-8679504683556796359
-8998431332432073156
-19039648549913072
2791383689640088810
-7006651425792604391
-3341403497186825424
4353782919667831842
7141543321281200614
4585094371098758049
-9074848149997010910
4261436059074692526
-6663411626186356594
-1024299272186580007
7305666140519153508
-1655410128264105669
-1282407367568826563

[Ritaf1983 · Accepted solution]

Hi @ArvindSh-MSFT 

In Power BI, very large integers (Int64/BigInt) cannot be displayed in full detail on charts. They are rounded for axis and label rendering to keep visuals readable. Only tables can show the full values without rounding.

As a workaround, you can duplicate the column, set it as text, and use that field when you need the exact number shown (for example as a label or tooltip). Keep in mind that charts still need the numeric column for calculations and aggregations — the text field is only for display purposes.

label_ = max('Table'[Value - Copy])

The pbix with the example is attached

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[govind_021 · Accepted solution]

Hi @ArvindSh-MSFT 

Power BI visuals internally use double-precision floating-point numbers, not 64-bit integers. Doubles can only represent about 15–16 digits of precision, while Int64 supports up to 19 digits. That’s why in visuals, slicers, and filters, large numbers appear rounded to the nearest 1000 even though the Table view shows the correct stored values. This isn’t data loss—just a rendering limitation of how visuals handle large integers.

You can try this
Duplicate the column in Power Query, convert the copy to Text, and use it in visuals (slicers, tables) to preserve exact display. Keep the original numeric column for calculations and DAX measures. This separates “calculation” from “display,” avoiding rounding while ensuring accurate math.

Best Regards
Govind Sapkade ( Microsoft Certified Data Analyst , PL 300 Certified , MS Fabric Enthusiast)
Let's Connect
Linkdin - www.linkedin.com/in/govind-sapkade-845104225
Youtube - http://www.youtube.com/@govind_dataanalyst

[Ritaf1983 · Accepted solution]

Hi @ArvindSh-MSFT 

In Power BI, very large integers (Int64/BigInt) cannot be displayed in full detail on charts. They are rounded for axis and label rendering to keep visuals readable. Only tables can show the full values without rounding.

As a workaround, you can duplicate the column, set it as text, and use that field when you need the exact number shown (for example as a label or tooltip). Keep in mind that charts still need the numeric column for calculations and aggregations — the text field is only for display purposes.

label_ = max('Table'[Value - Copy])

The pbix with the example is attached

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly