Release Notes Documentation   Issues with allocations after introducing default qty=1 on sales order (SO301000) and sales invoice (AR301000) in 9.05 In version 9.05 was introduced default qty=1 for sales orders (SO301000) and sales invoices (AR301000). Just after activating this in production, it came up that it gave issues for sales orders created via the POST salesorderv2 endpoint regarding allocations, leading to shipments not being possible to create. The issue has now been resolved and will reactivate the default qty=1 as standard again. There is one change compared to implementation done for version 9.05. Now the default quantity 1 is only set when you either POST a line with inventory ID, or if you in the UI select item ID on the line. For this reason adding lines without a reference to item will not automatically set the quantity to 1.     Invoice balance reset after Approved for payment field is updated via PUT SupplierInvoice endpoint Earlier, when the paySelected field was updated via PUT SupplierInvoice endpoint for an invoice partially paid, the open balance was reset to the initial balance available to pay. The issue has been fixed and the solution has been deployed under a feature toggle.       Due dates for breaking changes Release Notes Documentation Due Breaking change on Branch endpoint The following flags on the Branch endpoint will be set to false by default starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry Sep 13, 2022 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023 ... View more