[Release Notes] - Visma.Net API 9.03.0 - 28.06.2022

[#1]

Release Notes	Documentation
New endpoints for LotSerialClass	There are new endpoints for GET api/v1/lotserialclass/[classId] and GET api/v1/lotserialclass.
Not possible for any sales order to create two shipments from two different warehouses	Earlier, for any sales order, it was not possible to create two shipments to be sent from two different warehouses. This has now been fixed.
API JournalTransactionV2 now accepting subaccount segments containing spaces	Earlier, the JournalTransactionV2 did not accept Subaccount segments containing a space. This has now been fixed so that you can use "1" or "1 " if you have a segment with length 2, but it contains only one character It also works with a default sub containing a space. If you have a segment value starting with a space, that will not be accepted in the API or in the UI.

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 from 13th 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,