Help get this topic noticed by sharing it on Twitter, Facebook, or email.

API returns scientific notation, invalid for "numeric" data type

We recently started seeing some refresh errors (Invalid data for type "numeric".) on a managed package table and were able to trace the issue to some very small (or large) numeric values in a currency field being presented in scientific notation via the SFDC API. From what we have been able to determine, this is "Working as Design".

My question is, should we expect DBAmp to account for this, given that it is, apparently, just the way it is?

Current installed version is (3.5.4) on SQL Server 2016
1 person has
this question