I am also experiencing this on at least one customer today ... View more

Seems to be working again now, but we also saw a lot of these errors from yesterday afternoon until about 6:40 this morning. I don't see any incidents on https://status.visma.com/ either ... View more

Hello, The request worked properly in Postman. I have no idea why the same request does not work from azure logic app. I made a work around through an azure function and that works.   Best regards, Magnus ... View more

Hello, Which GET request are you referring to? Right now we are not doing any GET requests because our workflow is dependant on the POST returning the background action id. It was working up until october 22. and we did not make any changes to our code.   Best regards, Magnus ... View more

Hello Suzdar, Any updates on this? We are still struggling with this issue ... View more

Yes. And the customer is reporting that receipts are no longer being released. ... View more

I have also noticed missing webhooks. Shipment events. ... View more

Hello,   We ran into a problem here. The work around we implemented was to delete the original line, and then insert a new one, for example like this: PUT https://integration.visma.net/API/controller/api/v1/purchaseOrder/ { "lines": [ { "operation": "Insert", "project": { "value": "58" }, "projectTask": { "value": "100" }, "warehouse": { "value": "P" }, "account": { "value": "4010" }, "orderQty": { "value": 1 }, "inventory": { "value": "02" } } ] }  The problem is when the nonStock inventoryItem '02' has a default account which is not part of a project accounting group. In that case I get "Error: Inserting 'Purchase order line' record raised at least one error. Please review the errors.\r\nError: 'Project' cannot be empty". Was it always like this? I am pretty sure this worked a couple months ago, but I can't find anything related in the patch notes.   The reason the default account needs to not be project enabled is that otherwise the default project is null which is very frustrating for the user. ... View more

Hello! Any updates on this? We still have some stuff running on the old auth flow because of this issue.   Best regards, Magnus ... View more

Any updates on this? I can't find it in the backlogged ideas ... View more

Sounds good. If it gets flagged as a bug, do you have an idea of when it might be fixed? Its a key part of a customer solution we are building at the moment. Should I just go the replace line route? ... View more

I would like to add project and projectTask to the list of missing fields. Project is on the Get SO, but task is missing from lines. Neither of them are included in the Post/Patch endpoints.   Also as a side note, there is an extra comma causing a syntax error in the sample JSON for the Post salesorder endpoint   ... View more

I have a theory as to what might be happening here. Do you validate that the shipment exists before generating the report? That would explain why it works if there happens to exist a shipment with the same number as the receipt we are providing. ... View more

Sorry for the delay. I just sent an email with three examples   Magnus ... View more

As soon as the receipt has been released. I also experimented with a 30 seconds delay, but the issue persisted. ... View more

Sure. Here is a PUT Json that will work even if lotSerialNumber "123" is already used for this product { "shipmentDetailLines": [{ "operation": "Update", "lineNumber": { "value": 1 }, "allocations": [{ "operation": "Insert", "lineNbr": { "value": 0 }, "location": { "value": "1" }, "lotSerialNumber": { "value": "123" }, "quantity": { "value": 1 } } ] } ] }   ... View more