I am having trouble with the /controller/api/v1/supplierInvoice endpoint. Get range or specific invoice document is missing several line fields. ProjectTask, poReceiptNbr, poReceiptLineNbr to name a few. I tested a non-receipt linked invoice aswell, and that is missing projectTask.   This was working on monday. I don't see any release notes since then.   Is this a bug? Are there new expand queries I am supposed to use? Attached screenshots of gui and postman get result     ... View more

I have a PO line with a non-stock item, default cost account 4200. I try to update it with a PUT request and the following payload. I get a 204 response, but the line account is still 4200. {   "lines": [     {       "operation": "Update",       "lineNumber": {         "value": 1       },       "account": {         "value": "4080"       }     }   ] }   If I change the account to 4081 in the GUI and resend the same request, the account defaults back to 4200.    Is this a bug? Do I have to replace the line to achieve my goal? ... View more

Will salesorder_changed webhooks continue to fire the same way after the old sales order endpoints are disabled? Assuming they will, what about the resourceUri properties that are currently pointing to v1?   Adding an extra set of uri properties for v3 would be the most practical solution from our point of view. ... View more

My app is trying to account for purchaseReceipt release operation sometimes failing. I have a case where I get a 200 both in the background webhook, and when checking the stateLocation, however the receipt status is still balanced. Is this working as intended?     Original request: POST https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/000451/action/release response body: {   "id": "8b6bad6c-11d7-46ed-b79f-17fc63260765",   "stateLocation": "https://integration.visma.net/API/controller/api/v1/background/8b6bad6c-11d7-46ed-b79f-17fc63260765" }   received webhook: {   "id": "8b6bad6c-11d7-46ed-b79f-17fc63260765",   "statusCode": 200,   "stateLocation": "https://integration.visma.net/API/controller/api/v1/background/8b6bad6c-11d7-46ed-b79f-17fc63260765",   "contentLocation": "https://integration.visma.net/API/controller/api/v1/background/8b6bad6c-11d7-46ed-b79f-17fc63260765/content" }   stateLocation call: GET https://integration.visma.net/API/controller/api/v1/background/8b6bad6c-11d7-46ed-b79f-17fc63260765 response body: {   "id": "8b6bad6c-11d7-46ed-b79f-17fc63260765",   "status": "Finished",   "statusCode": 200,   "receivedUtc": "2022-11-14T11:30:11.726+01:00",   "startedUtc": "2022-11-14T11:30:11.773+01:00",   "finishedUtc": "2022-11-14T11:30:13.379+01:00",   "webhookAddress": "*sanitized*",   "originalUri": "https://finance.visma.net/**********/api/v1/PurchaseReceipt/000451/action/release",   "hasResponseContent": true,   "hasRequestContent": false,   "contentLocation": "https://integration.visma.net/API/controller/api/v1/background/8b6bad6c-11d7-46ed-b79f-17fc63260765/content" }   receipt 000451 is still Balanced.     ... View more

I am receiving feedback to my erp-api-background url, but when I try to poll the stateLocation or contentLocations I get a 403 response.      ... View more

We are observing strange behavior with API/controller/api/v1/employee for a fresh client.   After adding two employees in the gui, we are unable to see them in the API if we authenticate with users granted access to this client today. However, a user that has had access for a week already can find the employees OK. The user access rights is identical, both in admin/odp and user roles in SM201010. There are no access rights enabled.   Asking for a specific employee number returns 404, and a general get returns an empty array.   If that's not strange enough, we have webhooks enabled for employee_changed, and when we first created the two employees, the get call back to the resourceUri of one of the employees actually worked. When changing the same employee again however, we get 404.       ... View more