Update released supplier invoice (continued)

[Anonymous]

Continued from https://www.visma.com/software/support/portal/forum/showthread.php?12670-PENDING-Update-released-sup...

Trying to understand how to use this in a good way. If we were to always use the ft=1 parameter, I guess we would not get any errors that we would like to have. So should this maybe just be used if we get an error?

And when I tried using the same method on supplier credit notes, I didn't get it to work.

To us, it seems that adding ft=1 makes the API use another validation/business logic?

[Yıldırım · Accepted solution]

Hello, 
using FT=1 via API will allow you to update the exposed fields which are editable in the Supplier Invoice UI once the invoice is released. However, this is not working with "paymentMessage" "cashAccount".  We'll inform the team for reviewing this implementation to improve usability.


PUT: https://integration.visma.net/API/controller/api/v1/supplierInvoice/{invoiceNBR}?FT=1

Can be used for Supplier Invoice:

{
    "description": {
        "value": "Updated via API after release "
    },
    "paymentMethod": {
        "value": "1"
    },
    "paymentRefNo": {
        "value": "REFNO"
    },
    "dueDate": {
        "value": "2020-11-12T14:57:09.087Z"
    },
    "cashDiscountDate": {
        "value": "2020-11-12T14:57:09.087Z"
    }
}

PUT: https://integration.visma.net/API/controller/api/v1/supplierInvoice/DebitAdj/{invoiceNbr}?FT=1

For Purchase Credit Note,  based on fields available in the UI after release and exposed ones via API
(Although available in the DTO, "cashAccount" is not updated, this will also be reported)

{
    "description": {
        "value": "FT=1 TEST"
    },
    "paymentMethod": {
        "value": "1"
    },
    "paymentRefNo": {
        "value": "REFNO"
    }
}