[Release Notes] - Visma.Net API 8.98.0 - 24.05.2022

[#1]

Release Notes	Documentation
GET inventory range and GET inventory specific endpoints now have support for returning LotSerialClass	Added support for returning LotSerialClass in GET api/v1/inventory/{inventoryNumber} and GET api/v1/inventory endpoints
Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch	At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. This change will be enforced starting the 30th of August 2022. The ones willing to switch to this new approach earlier can contact the partner service, support, or development team. The same applies for the ones wanting to keep the old approach after the 30th of August 2022.
Feature toggle for allocations showing an extra row (/erp/api/v1/purchasereceipt endpoint)	The issue with allocations that show an extra row has been fixed under a feature toggle. This occurs when a purchase receipt is created with POST Purchase receipt. The fix is only for the /erp/api/v1/purchasereceipt endpoint

Due dates for breaking changes

Release Notes	Documentation	Due
Breaking change on Inventory endpoint for GET operation - better error handling	In the current solution, if you try to filter on an attribute on inventory which does not exist, you get an empty JSON response. So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this. From version 8.97, the system will return 400 Bad Request for this operation, and gives an error message that the value you are trying to filter on does not exist. - Example: {"message":"Attribute 'ACTIVE' not found"}	Jun 07, 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