Visma.net Financials API updates for version 8.86.0 (March 2022)

[#1]

Release date for 8.86.0 version has been planned as 01/03/2022.
Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release.

Release Notes	Documentation
Improved performance on GET Inventory endpoint [Pilot Testing]	The performance of the GET Inventory endpoint has been improved, and it is currently in Pilot Testing. This will be tested by the volunteered clients. Please contact the Partner Service from your country if you would like to volunteer. Once the pilot testing phase is completed, the improvement will be enabled for everyone. (Will be announced)
Performance improvements on Dimension endpoints	The performance on the following Dimension endpoints has now been improved: GET/controller/api/v1/dimension/{dimensionId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/{valueId} GET/controller/api/v1/dimension/{dimensionId}/{segmentId}/publicid/{publicId}
Wrong "Location" URL returned after successful POST CustomerInvoice V2 request	Earlier, the wrong "Location" URL was returned after a successful POST CustomerInvoice V2 request. This has now been fixed.
"GreaterThanValue" query parameter not working with GET Shipment endpoint	Earlier, the "GreaterThanValue" query parameter was not documented as being deprecated for the GET Shipment endpoint. This has now been fixed.
Unable to update a customer's "Invoice Address" fields via PUT Customer endpoint	Earlier, in some circumstances, the PUT Customer endpoint did not update the customer's "Invoice Address" fields. This has now been fixed.
The "Packages" field exposed via ShipmentDTO (GET Shipment) is not populated	Earlier, the GET Shipment endpoint did not populate the "Packages" field. This has now been fixed.
Cost price and description of purchase receipts linked to purchase order	Earlier, when you created a purchase receipt and linked it to a purchase order with API, the cost price and description were retrieved from the item and not from the purchase order rows as they should. This has now been fixed and the cost price and description are retrieved from the purchase order rows for each item.
Activate feature "Transfer Order" to the "Transfer Receipt" via Purchase Receipt endpoint	Earlier, adding "Transfer Order" to the "Transfer Receipt" via the Purchase Receipt endpoint was not possible. Now you are able to use POST operation via PurchaseReceipt endpoint to create transfer receipts via API.
Update notes via API (PUT) on SupplierInvoice when status is "Open"	Earlier, updating notes via API (PUT) on SupplierInvoice endpoint, when the status of the document was "Open", was not possible. This has now been fixed.

Due dates for breaking changes

Release Notes	Documentation	Due
Breaking change on Inventory endpoint for GET operation	We will enforce paging on Inventory 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 Inventory, without specifying any paging, you will get the first 500 records only.	Apr 01, 2022
Breaking change on Project endpoint for GET operation	We will enforce paging 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.	Apr 01, 2022
Breaking change on JournalTransaction endpoint	The POST methods /api/v2/journaltransaction/{journalTransactionNumber}/attachment and /api/v2/journaltransaction/{journalTransactionNumber}/{lineNumber}/attachment are deprecated and will be removed on March 1st 2022. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber}/attachment	Mar 1, 2022