My Products
Help

[Release Notes] - Visma.Net API 8.92.0 - 12.04.2022

by Yıldırım (Updated ‎13-04-2022 17:59 by Yıldırım VISMA )
Release Notes Documentation

ProjectTransaction Endpoint(PUT/POST) with several lines sets the last occurring financialPeriod on all lines

In previous versions, when using the Project transaction endpoint to create or update a project transaction with multiple transaction lines that have different financial periods, the project transaction was not taking into account the specified financial periods. This has now been fixed.

Account and subaccount combination in restriction groups not working via API Customer creditNote V2 endpoint (POST)

Earlier, it was not possible to create a document via the API Customer Credit note V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP.
This has now been fixed.

Account and subaccount combination in restriction groups not working via API Customer Invoice V2 endpoint (POST)

Earlier, it was not possible to create a document via the API Customer Invoice V2 endpoint (POST), when using an account and subaccount combination existing in a restriction group configured within Visma.net ERP.
This has now been fixed.

 

Due dates for breaking changes

Release Notes Documentation Due

Breaking change on Inventory endpoint for GET operation - better errorhandling

In the current solution, if you try to filter on an attribute on inventory which does not exits, 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, we will start returning 400 Bad Request for this operation, and give an error message that the value you are trying to filter on does not exist.
-
Example:
{"message":"Attribute 'ACTIVE' not found"}
May 17, 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

Breaking change on Project endpoint for GET operation

Paging will be enforced on Project endpoint.
The ISV must start implementing paging on this endpoint as soon as possible. The default page size is planned to be set to 500.
If you do not specify a page size, you will get 500 records, and if you try to specify a higher number, you will only get 500 records.
Example: If you do a GET ALL on Project, without specifying any paging, you will get the first 500 records only.
May 01, 2022