Cost information (Unit cost etc.) not applied for non-stock items to sales order lines when order is posted via API endpoint https://salesorder.visma.net/api/v3/SalesOrders   Via UI there is no problem with cost information of non-stock items.   With stock items there is no problem   In the screenshot first row is from API and second row is manually inputted. Unit cost with Red highlight RRTT_0-1712252964917.png   And here is the JSON message: {"type":"OL","status":"Hold","date":"2024-04-03T11:42:23.0000","requestOn":"2024-04-09T00:00:00.0000","description":"LESELL","customer":{"id":"05148","refNo":"22353","order":"LESELL"},"billing":{"contact":{"name":"OMEGA-KODIT OY","attention":"Tommi Hietala","email":"[email protected]","phone1":"040-5390554"},"address":{"line1":"HAAPAKOSKENTIE 85","postalCode":"86600","city":"HAAPAVESI","countryId":"FI"}},"shipping":{"contact":{"name":"OMEGA-KODIT OY","attention":"Tommi Hietala","email":"[email protected]"},"address":{"line1":"HAAPAKOSKENTIE 85","postalCode":"86600","city":"HAAPAVESI","countryId":"FI"}},"orderLines":[{"inventoryId":"OM05NP","quantity":3}]}   And screenshot of the non-stock item: RRTT_1-1712253221775.png RRTT_2-1712253288959.png       ... View more

Sub accounts have not been applied to sales order rows since 13.3.2023 when order is posted via API ( https://integration.visma.net/API/controller/api/v2/salesorder) (10.3.2023 was last sales order without problems with sub accounts)   Via UI there is no problem with sub accounts.   Sub accounts are set to be applied behind sales person: RRTT_0-1681208768269.png RRTT_1-1681208907734.png   Customer is Hydro Extrusion Finland Oy (Company ID 1882757)   Here is sample message: {     "branchNumber": {         "value": 1     },     "customerOrder": {         "value": "LU00087456"     },     "customerRefNo": {         "value": "Sami.Ekholm"     },     "date": {         "value": "2023-04-11T06:05:54Z"     },     "description": {         "value": "lu;LU00087456;5637171594;LU00087456-1"     },     "gln": {         "value": "FI22544498"     },     "hold": {         "value": true     },     "lines": [         {             "branchNumber": {                 "value": 1             },             "externalLink": {                 "value": "1;L127192561;11311105;m"             },             "inventoryId": {                 "value": "11311105L6600HR1"             },             "lineNbr": {                 "value": 1             },             "note": {                 "value": "1\nProductionBatch:lsu50686691\nColor:SA716JR RAL 9016 INTERPON D1036\nEfiBarQuantity:1"             },             "operation": "Insert",             "quantity": {                 "value": 6.6             },             "requestedOn": {                 "value": "2023-04-18T12:00:00"             },             "shipOn": {                 "value": "2023-04-18T12:00:00"             }         }     ],     "note": {         "value": "Pakkausohje:Bundle pack / Wrap machine packing\nPurchPoolId:"     },     "orderType": {         "value": "SO"     },     "requestedOn": {         "value": "2023-04-18T12:00:00"     },     "soShippingAddress": {         "value": {             "addressLine1": {                 "value": "Korjalankatu 27"             },             "city": {                 "value": "KOUVOLA"             },             "countryId": {                 "value": "FIN"             },             "overrideAddress": [                 {                     "value": true                 },                 {                     "value": true                 }             ],             "postalCode": {                 "value": 45130             }         }     } }   These sub accounts are very important to customer. Their bookkeeper noticed the problem while closing last period.   ... View more

PUT operation to Shipment endpoint incorrectly clears shipmentDetailLines: "note" -fields, even the note field is not in the message. This is a big problem to our integration with mobile WMS systems. Here is an example of JSON message that clears (but should not) the row note of the first row in shipment: {   "shipmentType": {     "value": "Issue"   },   "container": {     "value": false   },   "shipmentDetailLines": [{     "operation": "Update",     "lineNumber": {       "value": 1     },     "shippedQty": {       "value": 0     },     "allocations": [{       "operation": "Update",       "lineNbr": {         "value": 2       },       "quantity": {         "value": 15       },       "uom": {         "value": "KPL"       },       "location": {         "value": "NI.3B"       }     }]   }],   "hold": {     "value": false   },   "shipmentPackageLines": [] } ... View more