[Release Notes] - Visma.Net API 9.12.0 - 30.08.2022

[#1]

Release Notes	Documentation
Line note exposed on the Journal transaction endpoint	Four methods in the JournalTransactionV2 endpoint now have the line note information exposed: - GET /controller/api/v2/journaltransaction/{journalTransactionNumber} - GET /controller/api/v2/journaltransaction - POST /controller/api/v2/journaltransaction - PUT/controller/api/v2/journaltransaction/{journalTransactionNumber}
Unable to update "componentID" via PUT KitSpecifications endpoint	Earlier, it was not possible to update "componentID" in an existing line of a kit specification via the PUT KitSpecifications endpoint. This has now been fixed.
Data not sorted correctly in GET Inventory request with Pagination and LastModifiedDateTime	Earlier, response data were not sorted correctly in a GET Inventory request with Pagination and a LastModifiedDateTime filtering. This has now been fixed.
Data not sorted correctly in GET Inventory request with Pagination and availabilityLastModifiedDateTime	Earlier, response data were not sorted correctly in a GET Inventory request with Pagination and a availabilityLastModifiedDateTime filtering. This has now been fixed.

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