Numeric custom field notation - API

When updating an opportunity through the API,  a phone number (10 digits) on a custom opportunity field that is numeric, it'll be transfomed to x.xxxxxxE+09

for example:
5530056707 is transformed to 5.530057E+09

 

Is there any way to prevent this?

Thanks

0

Comments

3 comments
  • Hi Oscar,

    I tested this scenario in our REST API 2.2 using Postman, I don't see the number was formatted into notation.  Could the value be converted when binding into the variable?  On the other hand, for phone number it might be best using string/text because if the leading digits are zeros, then your value will have missing digits.

     

    Regards,

    Kevin

    0
    Comment actions Permalink
  • When using the api to update a number, lets say 123456123456, the json response with the updated value is 123456127000, now on the web site of insightly it'll show 1.234561E+11.

    Problem is that we need the field to be numeric because we're integration Toky and it'll only recognize a numeric field.

    0
    Comment actions Permalink
  • Oscar,

    If the number exceeds certain digits, the database will store the number as float instead of integer.  That is why it is showing approximate numeral instead of exact numeral.  Unfortunately there is no way to change such low level behavior.  My recommendation is to use string data type or split the number into multiple number fields.

    Best,

    Kevin

    0
    Comment actions Permalink

Please sign in to leave a comment.