I'm bulk-uploading attachments to products.   Most work fine but for some where the file size is 8-10 megabyte the request never finishes (at least not in the 20minute timeout I have). The attachment is not added the product.   Adding the same document manually in the GUI takes ~5 seconds.   ... View more

When prepare invoice fails   POST: https://integration.visma.net/API/controller/api/v2/salesorderbasic/IN/{id}/action/prepareInvoice   it just returns {"message":"Error creating customer invoice. Error: Updating 'Sales order' record raised at least one error. Please review the errors.\r\n"}   Can you please fix this so we know where to do? ... View more

Kind of a strange problem.   We create invoices from orders like: * POST api/v3/salesorders * POST controller/api/v2/salesorderbasic/{orderType}/{orderNumber}/action/prepareInvoice * POST controller/api/v1/customerinvoice/{invoiceNumber}/action/release   this works fine but for not for credit invoices * POST api/v3/salesorders * POST controller/api/v2/salesorderbasic/{orderType}/{orderNumber}/action/prepareInvoice * POST controller/api/v1/customerCreditNote/{creditNoteNumber}/action/release   The credit invoice is not released, no error message, but can be released in the GUI. Also, a credit invoice created directly, i.e. not from order, can be released via API.   What can we do differently to work around this?   ... View more

I'm trying to create a Kit assembly POST: https://integration.visma.net/API/controller/api/v1/kitassembly Headers: { Accept: application/json Authorization: <hidden> Content-Type: application/json; charset=utf-8 Content-Length: 87 } { "type": "P", "itemId": { "value": "103" }, "revision": { "value": "1" }, "quantity": { "value": 1.0 } } but get this nonsense error message (how does the API know "103" is 1869032 if it doesn't exist) {"message":"VismaId: 52d00096-5b37-421d-b743-1b2fdc447ad9. Error creating kit assembly. Error: An error in processing of field Item ID value 1869032 Error: Item ID '1869032' cannot found in the system. Check whether you have access rights to this object."} Kit specification: { "kitInventoryID": "103 ", "revision": "1", "description": "test produktion", "isActive": true, "allowComponentAddition": false, "isNonStock": false, "createdDateTime": "2022-11-17T15:07:27.467", "lastModifiedDateTime": "2023-09-07T13:04:28.577", "stockComponentLines": [ { "lineNbr": 1, "componentID": "104 ", "componentQty": 1.0, "uom": "STYCK", "allowComponentQtyVariance": false, "disassemblyCoeff": 1.0, "allowComponentSubstitution": false, "description": "komponent 3" }, { "lineNbr": 2, "componentID": "105 ", "componentQty": 1.0, "uom": "STYCK", "allowComponentQtyVariance": false, "disassemblyCoeff": 1.0, "allowComponentSubstitution": false, "description": "komponent 4" } ], "nonStockComponentLines": [ { "lineNbr": 1, "componentID": "107 ", "componentQty": 1.0, "uom": "STYCK", "allowComponentQtyVariance": false, "description": "Arbetad tid/tim" } ] } All involved inventory number exists.   Creating the same kit assembly works fine i GUI.   ... View more

I randomly get some internal error message when posting journal transactions (like 1 in 20 or so). Error is on different requests every time. The same request works fine with 2 or 3 retries.   How do we proceed?   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-Id: |gF8GNmNHyO4=.c7571599_14. Content-Type: application/json; charset=utf-8 Content-Length: 2014 } {"transactionDate":{"value":"2023-09-01T00:00:00"},"financialPeriod":{"value":"202309"},"ledger":{"value":"1"},"currencyId":{"value":"SEK"},"description":{"value":"hidden"},"createVatTransaction":{"value":true},"skipVatAmountValidation":{"value":true},"journalTransactionLines":[{"operation":"Insert","accountNumber":{"value":"1513"},"transactionDescription":{"value":"hidden"},"debitAmountInCurrency":{"value":5172}},{"operation":"Insert","accountNumber":{"value":"2610"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":0},"vatId":{"value":"23"}},{"operation":"Insert","accountNumber":{"value":"3150"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":3136},"vatCodeId":{"value":"04"}},{"operation":"Insert","accountNumber":{"value":"2610"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":0},"vatId":{"value":"23"}},{"operation":"Insert","accountNumber":{"value":"3150"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":1720},"vatCodeId":{"value":"04"}},{"operation":"Insert","accountNumber":{"value":"2610"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":0},"vatId":{"value":"23"}},{"operation":"Insert","accountNumber":{"value":"3150"},"transactionDescription":{"value":"hidden"},"creditAmountInCurrency":{"value":316},"vatCodeId":{"value":"04"}}]} Response: 400 Bad Request Headers: { Date: Tue, 05 Sep 2023 11:42:50 GMT Server: Nginx Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 02a7a1a9-ccca-49ed-9237-149d395daaad 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_0045 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Mon, 04-Sep-2023 11:42:49 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } {"message":"VismaId: 02a7a1a9-ccca-49ed-9237-149d395daaad. Error creating journal transaction. Cannot insert the value NULL into column 'LedgerID', table 'ERP_SE_REAL_0045.dbo.GLTran'; column does not allow nulls. INSERT fails.\r\nThe statement has been terminated."}   ... View more