API Issue: when creating or updating a detail record via the API the data is written into wrong fields, it writes data that should be written into CONTSUPP->ADDRESS1 field into CONTSUPP->EXT field

Version 1

    Details


    API Issue: when creating or updating a detail record via the API the data is written into wrong fields, it writes data that should be written into CONTSUPP->ADDRESS1 field into CONTSUPP->EXT field

    The Integrating with GoldMine API Specifications and Examples documentation describes in p. 209 - Creating or Updating a Detail Record. As stated in the documentation we used the following scheme

    UField1 -> Title
    UField2 -> LinkAcct
    UField3 -> Country
    UField4 -> Zip
    UField5 -> Ext
    UField6 -> State
    UField7 -> Address1
    UField8 -> Address2

    [RESULT]
    When testing our code we recognized that data that should be written into CONTSUPP->ADDRESS1 field is written into CONTSUPP->EXT field


    Resolution


    [CAUSE]

    in GoldMine Premium Edition (GMPE) 8.5 the Details tab was changed and offers since then 12 customizable fields instead of previously 8 customizable fields



    The following are the fields mapping in the new API:
    UField1 -> Title
    UField2 -> LinkAcct
    UField3 -> Country
    UField4 -> Dear
    UField5 -> Fax
    UField6 -> Zip
    UField7 -> Ext
    UField8 -> State
    UField9 -> MergeCodes
    UField10 -> Address1
    UField11 -> Address2
    UField12 -> Address3

    [RESOLUTION]

    the code from the application accessing the GoldMine API needs to be adjusted to reflect the changes.