Loading

Data 360: Large Numbers Displayed in Data Cloud UI May Appear Rounded Due to JavaScript Precision Limits

Date de publication: Feb 3, 2026
Description

When working with numbers that exceed 15–16 digits, you may notice that the Data 360 (Formerly Data Cloud) UI displays rounded or imprecise values. This behavior is due to limitations in how JavaScript (used in browser rendering) handles large numbers, and not an issue with Data 360 itself. The full value is safely stored in the backend with complete accuracy.

For example, a number like:

12345678901234567890

might appear in the UI as:

12345678901234567000

This behavior can lead to confusion in scenarios where exact values are important for downstream processing, matching, or data auditing.

What’s Happening Behind the Scenes?

This issue arises from how JavaScript, which powers most modern browser UIs, handles numeric values. JavaScript uses the IEEE 754 double-precision floating-point format, which can only safely represent integers up to 2⁵³ - 1, or roughly 15 to 16 digits. Any digits beyond this are not guaranteed to be precise, and rounding can occur automatically during rendering. Importantly, this is a UI-level limitation, not a reflection of how Data 360 stores or processes your data.

Résolution

To avoid precision loss when working with large numeric identifiers such as customerID, accountNumber, or referenceId, store these values as text instead of numbers. Even though these values may be composed entirely of numbers, they are not meant for mathematical operations. These are unique identifiers, similar to a phone number or passport number. Its purpose is to be matched exactly, not added, averaged, or compared numerically. Storing them as text ensures, there is no rounding or truncation in the UI.

Workaround suggestions:

  • Consider storing very large numeric values as strings if exact character-by-character preservation is critical.

  • Use string-based storage for any field that:

    • Is used purely for identification or matching

    • Exceeds 15–16 digits

    • Should remain exact and unaltered throughout its lifecycle

  • If displaying the full value to users is necessary, format the field as text or use a string cast in any custom UI components.

Numéro d’article de la base de connaissances

005093789

 
Chargement
Salesforce Help | Article