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

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
Highlighted
Power Apps
Power Apps

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
Highlighted
Power Apps
Power Apps

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

View solution in original post

Highlighted

Hi @AndyPennell 

 

Thanks for clarifying that. 

 

Tim

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (11,295)