[Release Notes] - Visma.Net API 9.83.0 - 01-03-2024

[#1]

Release Notes	Documentation
Improved performance of PUT v1/purchaseorder/{purchaseOrderNumber]	The performance of the PUT v1/purchaseorder/{purchaseOrderNumber] endpoint has been improved. Updating lines is now approx. 40 % faster than before.
Fixed error message POST/controller/api/v1/PurchaseReceipt	Earlier, in some circumstances, the endpoint POST/controller/api/v1/Purchase returned an error message. This has now been fixed.
POST SalesOrder with TenantID authentication works normally again	POST SalesOrder with TenantID authentication no longer gives error message 'Object reference not set to an instance of an object.'.
Release of purchase invoice via API missing link to batch, invoice stuck in Balanced status	This specific problem occurred in some occasions during heavy API load together with overlapping actions, where the released purchase invoice may have incorrectly remained in the Balanced status after it was released via SupplierInvoice endpoint. In this scenario the full release operation was not able to finish. Meaning, even though the release process was successful and a batch was created, if the batch failed to link the documents (the Financial details tab not showing a link to the batch no.), due to this the purchase invoice document remained in the Balanced status. The fix has been added under a feature toggle and will be initially activated for specific companies only. Within the fix behaviour added a retry for the release from API, if the release fails due to concurrency. Fix will later be included into all companies.
Improved performance on GET SupplierInvoice endpoint	The performance of the GET SupplierInvoice endpoints has been improved. The issue that was found during activation earlier (Version 9.80) where some of the response fields were being excluded has now been fixed. The improved endpoint will be activated for all companies.

API - Due dates for breaking changes

Release Notes	Documentation	Due
Default expand toggle values in GET KitAssembly endpoint to be set to FALSE instead of TRUE	Expand toggle values that are currently set to TRUE by default will be changed to FALSE by default.	May 01, 2024
Planned removal of VNI authentication method	We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for...	Dec 31, 2023
Planned removal of Sales Order API endpoints	We plan to be functionally complete by Q3-2024 (30th of September 2024), thus new due date being end of Q4-2024(31st of December 2024). If any change would occur for this, we will announce that as soon as possible, 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	Dec 31, 2024