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
PowerApps Staff AndyPennell
PowerApps 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.

2 REPLIES 2
PowerApps Staff AndyPennell
PowerApps 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.

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
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

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

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

SecondImage

Power Platform Summit North America

Register by September 5 to save $200

Top Kudoed Authors
Users Online
Currently online: 48 members 4,692 guests
Recent signins:
Please welcome our newest community members: