[Release Notes] - Visma.Net API 9.71.0 - 21.11.2023

[#1]

Release Notes	Documentation
Prepare invoice action now exposed via the "SalesOrder" and "SalesOrderBasic" endpoints	Two new endpoints have been introduced for the action 'Prepare invoice' for sales orders: - v2/salesorderbasic/{SOType]/{SOOrderNumber]/action/prepareInvoice - v2/salesorder/{SOType]/{SOOrderNumber]/action/prepareInvoice If the action is successful, the 200 OK response includes a reference number to an invoice. For example: {     "referenceNumber": "002625",     "actionId": "f9496e2a-3319-4439-bf24-7f4ced2252e5",     "actionResult": "Done" }
POST SupplierInvoice “No access to branch” error when service API was used for the first time	When using Visma Service API token for the first with POST SupplierInvoice, the error “No access to branch” was returned and delay took place before a successful call could be made. This has now been fixed.
GET Expense Claim "Pagesize and TotalCount" not returned	Earlier, the metadata "Pagesize and TotalCount" were not returned in GET ExpenseClaim. This has now been fixed.
POST/salesOrder/action/createPurchaseOrder no longer returns 'tstamp cannot be empty'	Earlier, in some circumstances, POST/salesOrder/action/createPurchaseOrder returned the error message 'tstamp cannot be empty'. This has now been fixed.
POST SalesOrder via API v1 and v2 no longer creates sales order with incorrect currency	Earlier, when 'Enable currency override' was not selected for a customer, the POST SalesOrder endpoint still allowed a sales order to be created with a currency other than the default currency for the customer, which resulted in incorrect prices on the sales order. This has now been fixed for v1 and v2, and you will need to select 'Enable currency override' in the Customers (AR303000) window to be able to create a sales order with a currency other than the customer's default currency.

API - Due dates for breaking changes

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