If you have any questions & comments, please go to the case specific thread or post a new one to inform us about your inquiry in detail. You can also contact us via developersupport@visma.com (Zero-downtime Release) Release date for 8.32.0 version has been planned as 12/01/2021 Release plan & date may vary. We will keep you informed of any changes.   Release Notes Documentation Rot/Rut deduction (SE) support via the sales order GET/POST/PUT endpoints Rot/Rut deduction (SE) is now supported from the API via the sales order GET/POST/PUT endpoints. ... View more

This thread will be updated regularly up until the point of version-release. If you have any questions & comments, please go to the case specific thread or post a new one to inform us about your inquiry in detail. You can also contact us via developersupport@visma.com Release date for 8.31.0 version has been planned as 21/12/2020 Release plan & date may vary. We will keep you informed of any changes. Release Notes. Documentation Errors in the response returned from the ProjectTransaction endpoint In previous versions, the ProjectTransaction endpoint was not showing in the response message the CreditAccountGroup for the GET operation. Now this issue has been fixed.   ... View more

Release Notes. Documentation 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 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) 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. 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 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. 8.30.0 of Visma.net ERP version was a zero downtime deployment. Users were able to continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment have been notified about the possibility to move to the new version. ... View more

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. ... View more

  Release Notes. Documentation Get all projects in the Project endpoint  In the previous version, when using the Project endpoint, it was not possible to get all projects and the response message showed error. This has now been fixed.   The release has been successfully deployed. 8.29.3 of Visma.net ERP version was a zero downtime deployment. Users were able to continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment have been notified about the possibility to move to the new version. ... View more

Release date for 8.29.3 version has been planned as 10/12/2020 - 17:00 CET Release plan & date may vary. We will keep you informed of any changes. 8.29.3 of Visma.net ERP version will be no downtime release. Users can continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment will be notified about the possibility to move to a newer version. Release Notes Documentation Get all projects in the Project endpoint  In the previous version, when using the Project endpoint, it was not possible to get all projects and the response message showed error. This has now been fixed.   ... View more