(DataFlex) Demonstrates how to Handle Large Integers in JSON

See more JSON Examples

Demonstrates how to handle large integers in JSON. (Integers larger than what can fit in a 32-bit signed integer.)

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

Use ChilkatAx-win32.pkg

Procedure Test
    Handle hoJson
    Boolean iSuccess
    Integer iId
    String sAccountId
    String sTemp1

    // Let's say your JSON has this:

    // {
    // 	"id": 20000000001234567
    // }

    Get Create (RefClass(cComChilkatJsonObject)) To hoJson
    If (Not(IsComObjectCreated(hoJson))) Begin
        Send CreateComObject of hoJson
    End

    Get ComLoadFile Of hoJson "qa_data/json/large_int.json" To iSuccess
    If (iSuccess = False) Begin
        Get ComLastErrorText Of hoJson To sTemp1
        Showln sTemp1
        Procedure_Return
    End

    // The integer is too large for a 32-bit signed integer that is returned by IntOf.
    // The result will be something that wrapped around and could be negative.
    // In this case it would be: -543893881
    Get ComIntOf Of hoJson "id" To iId
    Showln "id: " iId

    // The solution is to read the integer value as a string, and then use the features in your programming language
    // to convert from a string to a 64-bit integer.
    // 
    // Alternatively, you may wish to simply hold the value as a string.  If, for example, the integer simply references
    // an order ID, an account ID, etc., then there's no need to convert to an integer value.  You're not going to be doing
    // mathematical operations on it anyway.  This is usually the case for large integers -- they typically exist
    // in JSON as an account ID.

    // You can get any JSON value as a string:
    Get ComStringOf Of hoJson "id" To sAccountId
    Showln "accountId: " sAccountId

    // Sample output:

    // id: -543893881
    // accountId: 20000000001234567


End_Procedure