Transfer orders and receipts, part 2

[Stefan Hult]

Hi

We have now learned, that when we POST a receipt connected to a transfer order we use the following, and it works fine. Thanks Magnus.

Now comes part 2, we want to use PUT to add new lines. 

We use the previous example and add the receipt number and the new line number.

And get this error back. We have tested different combination, but it all ends up with telling us the order number is missing.

Now, for those who wonder why we want to use PUT.
We have discovered that if you have a transferorder with many lines, you get a TimeOut when you try to POST the receipt. What we have seen is that somewhere between 10 and 20 lines work. If you have more that that you get a TimeOut.

We know for sure that if we POST a receipt of 10 lines it works. That's why we have to split the receipt and send the rest of the lines, 10 lines at a time, with a PUT.

Conclusion

We have two problems here.
1. Timeout in POST if a large number of lines.

2. Cant add lines to an existing receipt using PUT.

[Stefan Hult · Accepted solution]

After contact with Yildirim we realise there isn't any shortcut here.

This customer has a substantial number of transfer order lines and create them took a long time.

We then decided to use the background functionality, and it works fine.
New API feature: "erp-api-background" operation - Visma Community

[Yıldırım]

Hello Stefan, 

I can confirm the issue with the PUT request.  Seems like 

"transferOrderType": {"value": "TransferOrder"}

 is omitted when we try to Insert a new line in the PUT request, therefore it returns Error: SOOrderNbr 'xxx' cannot be found in the system instead of "TransferOrderNbr" 'xxx' .  This will be conveyed to the team.

• How many TransferOrderLines in total do you need to add to a single Purchase Receipt ?
• What is your current client side time-out value ? 
• Could you share the details of the transaction <ClientID, CompanyID, ipp-req-id> that has been timed-out, including the full JSON ?
  (developersupport@visma.com)

Thanks.

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

This issue has been resolved in  [Release Notes] - Visma.Net API 9.21.0 - 08.11.2022

[Stefan Hult]

Hi Yildirim

Thank, then we know we don't have to spend more time trying to make PUT to work.

• Number of transferOrderLines is between 70 -250 lines. The test we have used is on 74 lines.
• We have tried different timeout,  10, 20 and 50 minutes.
• Details will come by mail from the developer.

Thanks.