Efficy Overflow Q&A - Recent questions tagged remote-api

When inserting mail through JSON API, is it possible to fill MEMO with body of Mail

Wed, 03 Nov 2021 09:04:14 +0000

When inserting mail through JSON API, is it possible to fill MEMO with body of Mail just like the Outlook addin does this ?

Meaning : Is there a function in Efficy that does this or does the customer need to extract the body from the .eml file and then set the MEMO field in the normal (API) way ?

Alphanumeric field gives bizarre error in JSON API request

Thu, 14 Oct 2021 18:22:26 +0000

when executing the following request

[{
        "@name": "Edit",
        "entity": "Docu",
        "commit": "true",
        "closecontext": "true",
        "@func": [{
                "@name": "update",
                "@data": {
                    "NAME": "Klein testje 2021",
                    "F_DIENST": 6,
                    "F_TYPE": 70,
                    "F_ONTVANGSTWIJZE": 0,
                    "F_NR_AANGETEKEND": "220309282357",
                    "MEMOFORMATTED": 0,
                    "MEMO": "",
                    "F_STATUS": 0
                }
            }
        ]
    }
]

we get this error :

"#error": {
"errorcode": "EConvertError",
"errorstring": "'' is not a valid date and time"
}

The field F_NR_AANGETEKEND is the problem.
It's an alphanumeric field with a length of 32.

values like "" or "123" or "0" etc are no problem.
But values like this give the conversion error.
Is this a bug or is there another way how we can force the API to see the value as a string ?

This happens on a Efficy (Build 11.2.19857.0 2019-12-07 12:02)

Is it possible to pass a null value in JSON API request?

Wed, 19 Aug 2020 06:23:17 +0000

To create a company I'm using the following JSON API request:

[
{
"@name": "edit",
"entity": "Comp",
"key": 0,
"commit": true,
"@func": [
{
"@name": "update", 
"@data": 
{
"NAME": "Test 01",
"VAT": null
}
}
]
}
]

but getting "Unknown data type for field VAT" error:

[
    {
        "@name": "edit",
        "entity": "Comp",
        "commit": true,
        "@func": [
            {
                "@name": "update",
                "@data": {
                    "NAME": "Test 01",
                    "VAT": null
                },
                "#error": {
                    "errorcode": "EEfficyException",
                    "errorstring": "Unknown data type for field \"VAT\"",
                    "detail": "CORE-1326"
                }
            }
        ],
        "key": "13",
        "edithandle": "2",
        "#error": true
    },
    {
        "@name": "exception",
        "#error": {
            "errorcode": "EEfficyException",
            "errorstring": "Unknown data type for field \"VAT\"",
            "detail": "CORE-1326"
        }
    }
]

Is it possible to pass a null value somehow?
Skipping the line will make the request to work, but sometimes it is necessary to pass a null (not an empty string, 0, etc)

how to request via json api both a file name and it's contents by a key

Mon, 02 Mar 2020 07:08:17 +0000

When I use the following json to request an attachment to a document, the response contains the byte stream (base64 encoded), but not the name of the attachment, and not the mime type. In addition, I need to know the key of the document; only the key of the attachment is not sufficient.

[
{
"@name": "edit",
"entity": "Docu",
"key": 684362,
"closecontext": true,
"@func": [
{"@name": "attachment", "key": "888274_0"}
]
}
]

Preferably it would be possible to request the file name, mime type, and contents of an attachment only by it's key. Can this perhaps be accomplished by an array of requests?

Thanks in advance.

Remote API: Trouble linking a Case to a Document with JSON

Wed, 12 Feb 2020 12:39:13 +0000

Hi,

when I try to link a Case to a newly created Document I get the following error:

{
            "@name": "insertDetail",
            "detail": "Case",
            "detailKey": 31,
            "#error": {
                "errorcode": "EConvertError",
                "errorstring": "'' is not a valid floating point value"
            }
        }

I'm using the flowing to link the Case to the Document:

{
"@name": "insertDetail",
"detail": "Case",
"detailKey": 31
}

What could be the cause of this error?

PS. When I try to link in Efficy a Case to a Document I don't have any issues.

Best regards,
Jeroen

Insert an attachment through JSON?

Wed, 12 Feb 2020 09:19:07 +0000

Hi,

does anyone know how to insert an attachment through JSON?
I need this for a customer who wants to insert documents from a website.

Best regards,
Jeroen