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

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

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
secondImage

New Return to Workplace

Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.

August 2020 CYST Challenge

Check out the winners of the recent 'Can You Solve These?' community challenge!

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Check this Out

Helpful information

Featuring samples like Return to the Workplace and Emergency Response Applications

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Users online (3,943)