[Release Notes] - Visma.Net API 8.91.0 - 05.04.2022

[#1]

Release Notes	Documentation
The performance of the GET Inventory endpoint improved - For details	The performance of the GET Inventory endpoint has been improved, leading to quicker response time. This has been in pilot testing for several weeks now and will be enabled for all customers with version 8.91.0 of Visma.net ERP.
Breaking change on Inventory endpoint for GET operation - For details	Paging has been enforced on Inventory endpoint. The default page size is 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. With this improvement, pagesize can be increased to  5000 on this endpoint so that clients can fetch more data in a single request.
Error when changing project ID in Project management	Earlier, when changing the project ID in Visma.net Project Management service, the integration sync with Visma.net ERP was stopping, and an error was displayed. This has now been fixed.
New handling of subaccount segments in Post JournalTransactionsV2	In the Post JournalTransactionsV2 it is now possible to provide subsets of the subaccount segments. The omitted segments will be assigned the default values as specified in the General ledger preferences (GL102000) window. For transaction lines including a cash account, the default subaccount as specified in the Cash accounts (CA202000) will be applied.
PUT Location Endpoint returns HTTP "400" Bad request instead of "404" Not found when the asset is not found	PUT Location endpoint will from version 8.91.0 return "404-Not found" instead of "400-Bad request" when the asset is not found.

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 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.	May 01, 2022