cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Super User
Super User

Loss of precision with SQL Server BigInt data type

One thing I discovered is that if I attempt to save the value 9007199254740988 to a SQL Server BigInt field, the actual value that my app saves to the database is 9007199254740990.

 

This loss of precision surprised me. Although I'd expect floating point numbers to behave in this way, I thought that an integer data type should allow me to save and retrieve exact values.

 

Can someone confirm if this is a bug or expected behaviour?

1 ACCEPTED SOLUTION

Accepted Solutions
Power Apps Staff AndyPennell
Power Apps Staff

Re: Loss of precision with SQL Server BigInt data type

This is expected behavior. PA uses Javascript under the hood, and has the same limitations for numeric accuracy.

View solution in original post

2 REPLIES 2
Power Apps Staff AndyPennell
Power Apps Staff

Re: Loss of precision with SQL Server BigInt data type

This is expected behavior. PA uses Javascript under the hood, and has the same limitations for numeric accuracy.

View solution in original post

Highlighted
Super User
Super User

Re: Loss of precision with SQL Server BigInt data type

Hi @AndyPennell 

 

Thanks for clarifying that. 

 

Tim

Helpful resources

Announcements
thirdimage

Power Apps Super User Class of 2020

Check it out!

thirdimage

New Badges

Check it out!

thirdimage

Power Apps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

SecondImage

Difinity Conference

The largest Power BI, Power Platform, and Data conference in New Zealand

Top Solution Authors
Top Kudoed Authors
Users online (4,605)