I'm using this POST https://salesorder.visma.net/api/v3/SalesOrders  to create a sales order and I want to inform supplierId for a few items. When I try to do it I receive an error. Consulting Visma Swagger for V3, I found this:     To be able to send supplierId, I need to inform purchaseToOrder too. My problem here is that for some items I receive this error message: "Only non-stock items for which 'Require receipt' and 'Require shipment' are selected can have purchase order source".   I couldn't find a way to check if "Require Receipt" and "Require Shipment" are checked. How I can do this? Do we have some endpoint or property on Inventory endpoint (V1 or V3) that allow us to validate it? I need a way to check if my inventory item have both checked and will accept my purchaseOrderSource.   ... View more

Hi  I'm having a problem when creating credit notes. For example:  When I send some line with discountPercent  20.0 and discountAmountInCurrency -52.2 the line on the credit note is created with -20.0 and -52.2 . I'd like the percentage to be positive. Is there a business rule on the API for that?    Example of line: { "operation": "Insert", "description": { "value": "" }, "quantity": { "value": 1.0 }, "unitPriceInCurrency": { "value": 271.0 }, "accountNumber": { "value": "3011" }, "uom": { "value": "ST" }, "discountPercent": { "value": 20.0 }, "discountAmountInCurrency": { "value": -54.2 }, "subaccount": [ { "segmentId": 1, "segmentValue": "60" }, { "segmentId": 2, "segmentValue": "10231" }, { "segmentId": 3, "segmentValue": "2" } ] } ... View more

Hi    I'm having an error when trying to insert a customer invoice on Visma API.  The whole json is really long so I will share the part that matters the most for me, the invoice line that is causing the issue:    { "operation":"Insert", "inventoryNumber":{ "value":"1" }, "description":{ "value":"Servicebil" }, "quantity":{ "value":62.0 }, "unitPriceInCurrency":{ "value":8.5 }, "accountNumber":{ "value":"3011" }, "uom":{ "value":"KM" }, "subaccount":[ { "segmentId":1, "segmentValue":"20" }, { "segmentId":2, "segmentValue":"10598" }, { "segmentId":3, "segmentValue":"2" } ] }{ "operation":"Insert", "inventoryNumber":{ "value":"1" }, "description":{ "value":"Servicebil" }, "quantity":{ "value":62.0 }, "unitPriceInCurrency":{ "value":8.5 }, "accountNumber":{ "value":"3011" }, "uom":{ "value":"KM" }, "subaccount":[ { "segmentId":1, "segmentValue":"20" }, { "segmentId":2, "segmentValue":"10598" }, { "segmentId":3, "segmentValue":"2" } ] }   The error response from the API:  {"message":"Error: Inserting 'Customer transactions' record raised at least one error. Please review the errors.\r\nError: UoM 'KM' cannot be found in the system.\r\n"} So I made a request to the unitofmeasure endpoint to check if exists, and it does.  The same behavior is happening with the UoM ST and I.    Any idea what could be happening?   ... View more

Hi    I'm posting the following invoice to the API: {   "invoiceLines": [     {       "operation": "Insert",       "inventoryNumber": {         "value": "086L0767-TH"       },       "quantity": {         "value": 1       },       "uom": {         "value": "STK"       }     }   ],   "sendToAutoInvoice": {     "value": false   },   "customerNumber": {     "value": "00033"   },   "documentDate": {     "value": "2023-03-23"   },   "invoiceText": {     "value": "test"   } }   URL:  https://integration.visma.net/API/controller/api/v2/customerinvoice   I'm getting this error:  {     "message": "VismaId: 59d0f756-c85f-4b87-b0d9-cf4bbe2b54ca. Object reference not set to an instance of an object." }   According to the documentation these would be the required values to create the customer invoice.   I also tried to send an invoice number but I got the same message.  ... View more

Hey    I am facing an error when trying to get 10.000 registers in the endpoint CustomerSalesPrice in Visma API.  Considering that the API endpoint supports 1.000 per page I would need to make 10 requests in order to get all the data I need.  Even with me paginating the results (increasing the pageNumber) the API does not seem to recognize that it is a different request, falling into this rule below. https://ibb.co/2d87MDs    And here's the error description in the community https://ibb.co/wWWMJ8d    An important fact is that I'm developing in Brasil. My coworker from Sweden that is using the same company and parameters is not having this issue.  I've tested using our Sweden VPN but I had the same error.    Would someone know to inform if Visma has some kind of block based in the geolocation? Or how could I solve that?    Thank you ... View more