cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
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
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
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

Hi @AndyPennell 

 

Thanks for clarifying that. 

 

Tim

Helpful resources

Announcements
News & Announcements

Community Blog

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

Power Apps Community Call

Power Apps Community Call- January

Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST

PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.

secondImage

Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

Top Solution Authors
Top Kudoed Authors
Users online (3,465)