Supplier invoice is released twice

[Anonymous]

Hi, 

When we're releasing a supplier invoice (through /controller/api/v1/supplierInvoice/{invoiceNumber}/action/release) 

and the process takes unusually long the user occasionally tries to release the invoice again. This triggers the same action and in the end the invoice is released twice. Is this expected behaviour? 

For investigation purposes, this is an example for company 2037292:

First release action response: 

{"ActionId":"c1afae3d-ba33-4ae0-99b7-896fb79d3678","ActionResult":"InProcess","ErrorInfo":null}

Second release action response:

{"ActionId":"7d317a9a-cb21-4604-b50e-520e18455400","ActionResult":"InProcess","ErrorInfo":null}

/ André 

[Anonymous]

Hi, 

Both releases are done via the API. The invoice is booked twice in the ledger.

In this case it was almost an hour between the two calls. If the first action isn't finished when the second call is made, it should still return the error message posted above. 

[Magnus Johnsen]

Hi,

Could you please provide us with the following information to developersupport@visma.com and we'll forward it to the development team for investigation:

• All steps taken until issue occurs
• Screenshot of Supplier Invoice showing Financial Details : Batch NR
• Screenshot of Journal Transactions window(ScreenId=GL3010PL) showing the batches created for this invoice

[Yıldırım]

Hello,
Release action is async therefore this is not waiting for the process finishing before it returns the ultimate ActionResult.

Once the document released, can not be released again and it'd return
 

Please check the status of the document via either API GET request or in the UI. Once Invoice is released GL document will be automatically created as it can be seen below. (Financial Details > BatchNo.)

[Magnus Johnsen]

Hi,

Is it correct that both of these releases are done via the API? Or is one via the API and one via the UI?

What is the effect? Is it booked twice in the ledger?

We'll try to reproduce this on our end.