[Release Notes] - Visma.Net API 9.68.0 - 31.10.2023

[#1]

Release Notes	Documentation
Improvements in the GET Account API endpoints	There are improvements in the GET Account API endpoints. Both, the 'Get a specific account' and the 'Get a range of accounts' endpoint will include values for: - Control account module - Allow manual entry - Public code - External code 1 - External code 2 - Analysis code in their responses. In addition, it is possible to set filters on - Public code - External code 1 - External code 2 - Analysis code in the 'Get a range of accounts' endpoint.
GET v2/salesorder endpoint with use of pagination	The GET v2/salesorder endpoint with the use of pagination no longer returns the error "Divide by zero error encountered".

API - Due dates for breaking changes

Release Notes	Documentation	Due
Deprecated fields on Account endpoint	The following fields are deprecated and will be removed on 13th of February 2024:  - ExternalCode1  - ExternalCode2  - AnalysisCode They should be replaced by fields: ExternalCode1Info, ExternalCode2Info, AnalisysCodeInfo, which contain more details.	Feb 13, 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 Q2-2024 (30th of June 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