After the update yesterday I randomly get the error message "Invalid Token" when fetching shipments.   Nothing is changed on my side and the integration uses clientid/tenantid. Here are some request ids if it helps 2023-04-25 15:41:16.7347067: "26ff45f4-10ba-4cd9-9437-17111aeff6c2" 2023-04-24 17:01:16.5120711: "bacfd6c1-61b9-4a9a-a9f1-407e7af6169f" 2023-04-24 16:01:22.5099885: "2d9a33eb-2b1c-443a-baa3-2027e79fc380"         ... View more

This page says   "<etag_value>" Entity tag that uniquely represents the requested resource. It is a string of ASCII characters placed between double quotes, like "675af34563dc-tr34"     The sales order API send ETag header without quotes so it is not parsed correctly in e.g .Net HttpResponseMessage   Same problem with if-Match. Sales Order API does not accept a quoted etag. ... View more

Has something changed in the API recently?   I can no longer create "TR" orders.   SalesOrdApi just return 500 "Internal Server Error" without message. VismaNetApi returns "'Destination warehouse' cannot be empty." I can't find Destination warehouse in Swagger and the Idea to add it is still open.   Same code worked 2 weeks ago.   SalesOrderApi POST: https://salesorder.visma.net/api/v3/SalesOrders Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Context: appId=cid-v1:72b1579a-9e83-44d4-b964-8b83e2853ccd Request-Id: |69aee49e69c625d9114b764d86d1b7ed.389ae70310f70584. traceparent: 00-69aee49e69c625d9114b764d86d1b7ed-389ae70310f70584-00 Content-Type: application/json; charset=utf-8 Content-Length: 291 } { "type": "TR", "date": "2023-03-08T07:00:00", "description": "23247", "status": "Hold", "customer": { "id": "10003" }, "orderLines": [ { "inventoryId": "017092000", "quantity": 1.0, "warehouseId": "1", "subaccount": { "1": "00" } }, { "inventoryId": "008456000", "quantity": 1.0, "warehouseId": "1", "subaccount": { "1": "00" } } ] } Response: 500 Internal Server Error Headers: { Date: Thu, 09 Mar 2023 10:30:28 GMT Connection: keep-alive apigw-requestid: BglCZgQrAi0EJrQ= Content-Length: 0 }    VismaNetApi POST: https://integration.visma.net/API/controller/api/v2/salesorder Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Context: appId=cid-v1:72b1579a-9e83-44d4-b964-8b83e2853ccd Request-Id: |8e4e4e8700207121bbff8ab808ac205a.ce06f9725f4d6eee. traceparent: 00-8e4e4e8700207121bbff8ab808ac205a-ce06f9725f4d6eee-00 Content-Type: application/json; charset=utf-8 Content-Length: 525 } { "lines": [ { "subaccount": [ { "segmentId": 1, "segmentValue": "00" } ], "operation": "Insert", "inventoryNumber": { "value": "017092000" }, "warehouse": { "value": "1" }, "quantity": { "value": 1.0 } }, { "subaccount": [ { "segmentId": 1, "segmentValue": "00" } ], "operation": "Insert", "inventoryNumber": { "value": "008456000" }, "warehouse": { "value": "1" }, "quantity": { "value": 1.0 } } ], "orderType": { "value": "TR" }, "hold": { "value": true }, "date": { "value": "2023-03-08T07:00:00" }, "customer": { "value": "10003" }, "description": { "value": "23247" } } Response: 400 Bad Request Headers: { Date: Thu, 09 Mar 2023 10:43:09 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 2d8260f7-ef4e-4481-8bd3-123dd7069afb X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_DEMO_0017 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Wed, 08-Mar-2023 10:43:04 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } {"message":"Error: Inserting 'Sales order' record raised at least one error. Please review the errors.\r\nError: 'Destination warehouse' cannot be empty.\r\n"}   ... View more

The Visma.Net Api once again had a major update (9.32 -> 9.33) without any advance notification or release notes.   I noticed it on friday last week but don't know when it happened.   Is this the new normal?       ... View more

(third try, 2 earlier posts has been marked as spam)   I have made several hundred calls to the journal transaction endpoint yesterday and today. 25% of them fails with code 400. Exactly the same request works on second (or third) try. What can I do? (this is a new integration so I don't have any history) Tenant id is 192de558-8750-11ed-9891-0693d8a7c3dd   Visma.Net: POST: https://integration.visma.net/API/controller/api/v2/journaltransaction Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Context: appId=cid-v1:72b1579a-9e83-44d4-b964-8b83e2853ccd Request-Id: |0ff99bcdd38f07fd14dc396339c307d5.084fcdecf5dc5bd5. traceparent: 00-0ff99bcdd38f07fd14dc396339c307d5-084fcdecf5dc5bd5-00 Content-Type: application/json; charset=utf-8 Content-Length: 662 } { "transactionDate": { "value": "2023-01-05T00:00:00" }, "ledger": { "value": "1" }, "description": { "value": "11040" }, "journalTransactionLines": [ { "operation": "Insert", "accountNumber": { "value": "1943" }, "subaccount": [ { "segmentId": 1, "segmentValue": "000" }, { "segmentId": 2, "segmentValue": "00000" }, { "segmentId": 3, "segmentValue": "000" } ], "debitAmountInCurrency": { "value": 100.0 }, "creditAmountInCurrency": { "value": 0.0 } }, { "operation": "Insert", "accountNumber": { "value": "3110" }, "subaccount": [ { "segmentId": 1, "segmentValue": "360" }, { "segmentId": 2, "segmentValue": "36100" }, { "segmentId": 3, "segmentValue": "000" } ], "debitAmountInCurrency": { "value": 0.0 }, "creditAmountInCurrency": { "value": 100.0 } } ] } Response: 400 Bad Request Headers: { Date: Mon, 30 Jan 2023 14:08:36 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 29b050ef-21ad-4daa-9c54-d3571552cb75 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_REAL_0042 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Sun, 29-Jan-2023 14:08:35 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } { "message": "VismaId: 29b050ef-21ad-4daa-9c54-d3571552cb75. Error creating journal transaction. Cannot insert the value NULL into column 'LedgerID', table 'ERP_SE_REAL_0042.dbo.GLTran'; column does not allow nulls. INSERT fails.\r\nThe statement has been terminated." }   ... View more

I have made about 50 calls to the journal transaction endpoint today. 25% of them fails with code 400. Exactly the same request works on second try. What can I do? (this is a new integration so I don't have any history) Tenant id is 192de558-8750-11ed-9891-0693d8a7c3dd   (sorry for the formatting. If I add it as code the post is marked as spam) Visma.Net: POST: https://integration.visma.net/API/controller/api/v2/journaltransaction Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Context: appId=cid-v1:72b1579a-9e83-44d4-b964-8b83e2853ccd Request-Id: |0ff99bcdd38f07fd14dc396339c307d5.084fcdecf5dc5bd5. traceparent: 00-0ff99bcdd38f07fd14dc396339c307d5-084fcdecf5dc5bd5-00 Content-Type: application/json; charset=utf-8 Content-Length: 662 } { "transactionDate": { "value": "2023-01-05T00:00:00" }, "ledger": { "value": "1" }, "description": { "value": "11040" }, "journalTransactionLines": [ { "operation": "Insert", "accountNumber": { "value": "1943" }, "subaccount": [ { "segmentId": 1, "segmentValue": "000" }, { "segmentId": 2, "segmentValue": "00000" }, { "segmentId": 3, "segmentValue": "000" } ], "debitAmountInCurrency": { "value": 100.0 }, "creditAmountInCurrency": { "value": 0.0 } }, { "operation": "Insert", "accountNumber": { "value": "3110" }, "subaccount": [ { "segmentId": 1, "segmentValue": "360" }, { "segmentId": 2, "segmentValue": "36100" }, { "segmentId": 3, "segmentValue": "000" } ], "debitAmountInCurrency": { "value": 0.0 }, "creditAmountInCurrency": { "value": 100.0 } } ] } Response: 400 Bad Request Headers: { Date: Mon, 30 Jan 2023 14:08:36 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 29b050ef-21ad-4daa-9c54-d3571552cb75 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_REAL_0042 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Sun, 29-Jan-2023 14:08:35 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } { "message": "VismaId: 29b050ef-21ad-4daa-9c54-d3571552cb75. Error creating journal transaction. Cannot insert the value NULL into column 'LedgerID', table 'ERP_SE_REAL_0042.dbo.GLTran'; column does not allow nulls. INSERT fails.\r\nThe statement has been terminated." }     ... View more

We sometimes have webhooks with very different functionality on e.g. sales order in the same company.   Some are listening for status changes while others are listening for actions (menu items).   Currently we need to put all this functionality into the same subscription which makes it difficult to maintain and reuse. (or subscribe with different users)   ... View more

* An order has a single open shipment with a single line * Delete the line on the shipment in GUI   The order get status "Open"   If the line is deleted via API the order status remains "Delivered" (Using Shipment endpoint and line operation "Delete")   It can be corrected in the GUI by * Mark Hold * Hold is automatically removed and status is changed to "BackOrder" * Mark Hold again * Save order * Order status is changed to Hold * Remove Hold * Order status is changed to "Open"   (Actually I would like to delete the entire shipment but there is no delete on the shipment endpoint)   ... View more

I have a webhook receiver in Azure which is never triggered. If I run the hook receiver in my own network instead it works fine. It also works if I manually post with curl to the (Azure) hook receiver from my machine. I have other similar Azure hook receivers which works fine. I'm sure I have done something stupid or missed some configuration but I am out of ideas where to look. Can you see what response this hook got? Visma.Net shows {"EntityId":"e08f35c8-fa82-42c0-8c78-3e3473ee1165", "NotificationId":"a9c45d9e-24d4-4e2e-bd69-1827f6017ff1", "EntityLocation":"api/v1/salesorder/4300078", "Event":"SalesOrder_Action_Triggered", "ActionCommand":"https://<hidden>.azurewebsites.net/api/CalculateFreight", "TimeStamp":"638097334481200000", "ApiClientId":null, "TenantId":"bb504cc1-6034-11ed-98d8-06a0b4eada6b", "ConnectId":"385e779c-4b1d-4d64-ac86-7be9ae96f448", "IsScheduler":false} (also curious why the json displayed in Visma.Net is not the same as the one sent)     ... View more

With tenant id GET: https://integration.visma.net/API/resources/v1/subscription Headers: { Accept: application/json Authorization: <hidden> } Response: 400 Bad Request Headers: { Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 3aa89978-1070-4f6d-8d16-1d9960faf756 Connection: close Date: Tue, 17 Jan 2023 11:41:16 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Content-Length: 208 Content-Type: application/json } {"ExceptionType":"IPPException","ExceptionMessage":"Invalid parameter exception: ipp-company-id","ExceptionFaultCode":"12002","ExceptionMessageID":"ec6ffb08-30f6-4b65-baec-46b9c8c08806","ExceptionDetails":""}   With token GET: https://integration.visma.net/API/resources/v1/subscription Headers: { Accept: application/json Authorization: <hidden> ipp-application-type: Visma.net Financials ipp-company-id: 4457075 } Response: 200 OK Headers: { Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: e7d040b7-99e9-4774-a973-f3dc4d856e9f Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Date: Tue, 17 Jan 2023 11:46:45 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Content-Length: 2 Content-Type: application/json } [] ... View more