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?
Solved! Go to Solution.
This is expected behavior. PA uses Javascript under the hood, and has the same limitations for numeric accuracy.
This is expected behavior. PA uses Javascript under the hood, and has the same limitations for numeric accuracy.
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
User | Count |
---|---|
196 | |
176 | |
62 | |
34 | |
32 |
User | Count |
---|---|
343 | |
271 | |
112 | |
75 | |
59 |