My Products

[Release Notes] - Visma.Net API 9.80.0 - 06.02.2024

by Sandra Anté (Updated ‎09-02-2024 15:06 by Yıldırım VISMA )
Release Notes Documentation

Unspecified subaccount segments now replaced with default segment values when creating documents via CustomerInvoice endpoint

When you create documents with partially set subaccount segment values via the CustomerInvoice endpoint POST operation, the system will now replace the unspecified segments with default segment values. The default segment values are retrieved according to the setting 'Combine sales sub. from' in the Customer ledger preferences (AR101000) window.

Improved performance on GET SupplierInvoice endpoint

The performance of the GET SupplierInvoice endpoints has been improved.

Issues that were found with some of the available parameters during earlier activation have 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

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 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:
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 ERP Sales Order Service, please visit:

Swagger for
Dec 31, 2024