Visma.net Financials API updates for version 8.30.0 (December 2020)

[#1]

Release date for 8.30.0 version has been planned as 15/12/2020
Release plan & date may vary. We will keep you informed of any changes.

Version 8.30.0 of Visma.net ERP will be deployed at 20:00 CET
Users can continue working in the system during the upgrade. The ones that are actively using the system will be notified about the possibility to move to a newer version.

Release Notes.	Documentation
Purchase invoices with a leading space in the reference number	Previously, it was possible to create purchase invoices with a leading space in the reference number using manual numbering, and that caused data corruption. This has now been fixed.
Unable to update fields in a released Sales Invoices(Debit note) via API	Earlier, there were some fields in the debit note that could not be updated via API (PUT api/v1/customerDebitNote/{debitNoteNumber}), after the debit note was released. This has now been fixed. (cashDiscountDate, documentDueDate, paymentMethodId and cashAccount)
Set another max. page size for GeneralLedgerTransaction and Balance endpoints	Previously, the MaxPageSize setting was common for the entire API. We were not able to change it just for a certain endpoint. Because the general ledger endpoints export a big amount of data, sometimes we want to increase the MaxPageSize only for those endpoints to speed up the data transfer. Now we introduced an individual MaxpageSize setting for GeneralLedgerTransactions, GeneralLedgerBalanceV2 and JournalTransactionV2
Unable to update fields in the released Sales invoices (AR301000) window via API	Earlier, some fields in the Sales invoices (AR301000) window could not be updated through the API, after the invoice was released. This has now been fixed, so that the fields "documentDueDate", "cashDiscountDate", "paymentMethod" and "cashAccount" are updated when using the PUT method for the customerInvoice API.
PUT Inventory returns "tstamp" cannot be empty"	Earlier, the PUT/api/v1/inventory method sometimes returned an error message regarding "tstamp", when item classes had 'Replenishment settings' added. This has now been fixed.