[Release Notes] - Visma.Net API 9.20.0 - 01.11.2022

[#1]

Release Notes	Documentation
New GET endpoints in the API for Fixed Asset	New GET endpoints in the API for Fixed Asset: fixedAsset fixedAsset/{assetID} fixedAssetTransaction fixedAssetTransaction/{RefNo} fixedAssetClass fixedAssetClass/{classID} fixedAssetPropertyTaxGroup (NL only) fixedAssetPropertyTaxGroup/{propertyTaxID} (NL only)
Webhook for salesorder wrongfully triggered for response status 4xx or 5xx when creating shipment via POST endpoint  /controller/api/v2/salesorder/{saleOrderNumber}/action/createShipment	When you try to create a shipment for a specific sales order with not all lines available in stock, you will no longer get a wrongful webhook notification indicating the sales order status has changed to status 'Shipping'.
SalesOrder endpoint returned 500 Internal Server Error instead of 400 Bad Request	The POST SalesOrder endpoint now returns the correct 400 Bad Request error instead of the incorrect 500 Internal Server Error when you try to create a sales order with a previously used sales order number.
Wrong response status 500 when creating shipment via POST endpoint  /controller/api/v2/salesorder/{saleOrderNumber}/action/createShipment	When you try to create a shipment for a specific sales order with not all lines available in stock and option "Ship only when complete", you will no longer get the incorrect error response status 500, but a 409 (Conflict) with descriptive message instead.
POST PurchaseReceipt and PUT PurchaseReceipt endpoints return error	The endpoints POST PurchaseReceipt and PUT PurchaseReceipt no longer incorrectly return an error when the content contains "landedCost".
POST PurchaseOrderReceiptBasic endpoint fails in some circumstances	Earlier, the POST PurchaseOrderReceiptBasic endpoint was failing in some circumstances. This has now been fixed.

Due dates for breaking changes

Release Notes	Documentation	Due
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