[Release Notes] - Visma.Net API 8.89.0 - 22.03.2022

[#1]

Release Notes	Documentation
Improved performance on GET ALL Supplier endpoint	The performance of the GET ALL Supplier endpoint has been improved. The pilot testing phase is now completed, the improvement which has been deployed under a feature toggle is now enabled for all customers in production.
Change in MaxPageSize for the GET Inventory endpoint	MaxPageSize for GET Inventory will be set to 5000 from 1 April 2022.
Validate syntax of provided webhook address in API request with erp-api-background	Earlier, the webhook address provided in the erp-api-background request header has not been validated, therefore, it was causing an exception if a bad URL was provided. This has now been fixed.
Possible to insert invalid value in "type" when using PUT Inventory endpoint and make the item invalid	Earlier, it was possible to insert an invalid value in "type" when using the PUT Inventory endpoint. This has now been fixed.
Account and subaccount combination in restriction groups not working via API SupplierInvoice endpoint (POST)	Earlier, creating a document via the API SupplierInvoice endpoint (POST) using an account and subaccount combination existing in a restriction group configured within Visma.net ERP was not possible. This has now been fixed.
RoundingDifference omitted when using SupplierInvoice endpoint (POST)	Earlier, in some circumstances, the RoundingDifference amount was omitted when creating an invoice via the SupplierInvoice endpoint (POST). This has now been fixed, and the solution is under a feature toggle.
Allow purchaseReceipt action addPurchaseOrder to add purchase orders of type drop-ship	Earlier, you were not able to add drop-shipments to Poreceipt through POST/controller/api/v1/PurchaseReceipt/{receiptNumber}/action/addpurchaseorder. This has now been fixed by adding orderType to the JSON-file: {   "purchaseOrders": [     {       "orderNbr": "string",       "orderType": "RegularOrder"     }   ] } OrderType needed to be changed to DropShip to get drop-shipments to work.

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
Breaking change on Location endpoint for PUT operation	PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found.	Apr 05, 2022
Breaking change on Inventory endpoint for GET operation	Paging will be enforced on Inventory endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 5000. If you do not specify a page size, you will get 5000 records, and if you try to specify a higher number, you will only get 5000 records. Example: If you do a GET ALL on Inventory, without specifying any paging, you will get the first 5000 records only.	Apr 01, 2022
Breaking change on Project endpoint for GET operation	Paging will be enforced on Project endpoint. The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500. If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records. Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only.	Apr 01, 2022