Visualisations Incorrectly Displaying Large Integers

[mdferris]

When displaying a large integer (in my case a BIGINT from a SQL Azure Db), visualisations appear to truncate the value to somethis less precise.  I have observed this in tables and the Text Filter slicer.

For example, the following value is correctly stored in the dataset:

-5355371827972002325

However in visualisations it is truncated to:

-5355371827972003000

This means incorrect values are being displayed, but also means the Text Filter does not work on such fields as the value that is used to search differs from that entered and does not match the underlying dataset.

[v-qiuyu-msft]

Hi @mdferris ,

I have reported this issue internally: CRI 105793605. Will update here once I get any information. 

Best Regards,
Qiuyun Yu 

[v-qiuyu-msft]

Hi @mdferris ,

I got information below: 

"5355371827972002325 is larger than 9007199254740991 (MAX_SAFE_INTEGER in JavaScript)

console.log(Number.MAX_SAFE_INTEGER);
// expected output: 9007199254740991

The Number.MAX_SAFE_INTEGER constant represents the maximum safe integer in JavaScript (253 - 1).

The reasoning behind that number is that JavaScript uses double-precision floating-point format numbers as specified in IEEE 754 and can only safely represent numbers between -(253 - 1) and 253 - 1.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INT..."

Best regards,
Qiuyun Yu 

[ToddChitt]

I know this is old content, but SERIOUSLY? I am using BIGINT data type in a Fabric Warehouse because the data is in the magnitude of 800000000001106000 (that's 18 digits). Per Microsoft's own documentation here: https://learn.microsoft.com/en-us/sql/t-sql/data-types/int-bigint-smallint-and-tinyint-transact-sql?... the max value of BIGINT is 9223372036854775807 (19 decimals) From what I can tell, the actual data model is behaving, in that the relationships that use the BIGINT columns are doing what we expect, but we can't DISPLAY that many decimals? That's horrible!