Release date for 8.46.0 version has been planned as 27/04/2021 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 JournalTransaction endpoint deprecated and replaced with new one The JournalTransaction endpoint is deprecated, and it has now been removed. A new endpoint was created to replace it.  See the Swagger documentation for more information under the 'JournalTransactionV2' endpoint. API POST calls returned incorrect location for credit note, credit adjustment or prepayment When sending POST > credit note, credit adjustment, or prepayment via API, the system returned an incorrect location after booking the invoice in the ERP. For example: Instead of returning: controller/api/v1/supplierInvoice/Prepayment/{ref. number} the System returned: controller/api/v1/supplierInvoice/{ref. number} By not adding the document type in the URL, you would not have been able to find your document just created, because your location would have returned a "404 not found" error. This issue has now been fixed and the system returns the correct location. ... View more

Planned start date: April 17th 2021, 20:00 CEST Planned end date: April 17th 2021, 21:00 CEST Expected downtime for Visma.net ERP, Visma.net ERP API. Status can be followed at: https://status.visma.com/incidents/q890lq3mmc9m A minor maintenance has been planned for Visma.net ERP. We'll be using this time to perform an upgrade of DNS servers.  We expect downtime, so we ask that you to plan your integrations accordingly, and we're sorry for any standstill this may cause. Thank you for your understanding. ... View more

Release Notes Documentation Missing subaccount description API post subaccount In earlier versions, when a default language was set in the System locals (SM200550) window under 'Set up languages', there was an error in using the API endpoint Post subaccounts. The subaccount description text was omitted and not visible in the Description field in the Subaccounts (GL203000) window. This has now been fixed. Due dates for breaking changes Release Notes. Documentation Due JournalTransaction endpoint deprecated and replaced with new one The JournalTransaction endpoint is deprecated and will be removed on April 27th 2021. A new endpoint was created to replace it. You find the documentation in Swagger under the 'JournalTransactionV2' endpoint. Apr 27, 2021 ... View more

Release date for 8.44.0 version has been planned as 13/04/2021 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.   Due dates for breaking changes: Documentation Due  The 'JournalTransaction' endpoint is deprecated and will be removed on April 27th 2021. A new endpoint was created to replace it. You find the documentation in Swagger under the 'JournalTransactionV2' endpoint. Apr 27, 2021   Release Notes Documentation Missing subaccount description API post subaccount In earlier versions, when a default language was set in the System locals (SM200550) window under 'Set up languages', there was an error in using the API endpoint Post subaccounts. The subaccount description text was omitted and not visible in the Description field in the Subaccounts (GL203000) window. This has now been fixed. ... View more

Release Notes Documentation New endpoints for Organization (Companies) There are the following new endpoints for the company: - GET organization/{organizationNumber}, - GET organization - PUT organization/banksettings The API returns the same information as for branches. In addition, there are settings for getting branches and bank settings. Payment settings added in the Branch API A PUT Branch/Banksettings has also been added where you can update Bank information. The following columns on the tab Payment settings can be updated: bankName bankAddress1 bankAddress2 bankAddress3 bankCountry iban bban bbaN2 bbaN3 bic creditorId   Expose branch Payment settings tab in Branch endpoints The Branch APIs have been changed and the expandBanksettings parameter can be set to get Bank information from the branches. The following columns on the tab Payment settings will be returned: bankName bankAddress1 bankAddress2 bankAddress3 bankCountry iban bban bbaN2 bbaN3 bic creditorId   Wrong status when updating the sales order where the customer has exceeded its credit limit Earlier, when a customer had exceeded its credit limit and when you updated a sales order using PUT /api/v1/salesorder/{salesorderNumber} from status "Hold", the status didn't change to "Credit hold". Instead, it changed to "Open". This has now been fixed, so it works exactly as in the user interface. ... View more

Release date for 8.43.0 version has been planned as 06/04/2021 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 New endpoints for Organization (Companies) There are the following new endpoints for the company: - GET organization/{organizationNumber}, - GET organization - PUT organization/banksettings The API returns the same information as for branches. In addition, there are settings for getting branches and bank settings. Payment settings added in the Branch API A PUT Branch/Banksettings has also been added where you can update Bank information. The following columns on the tab Payment settings can be updated: bankName bankAddress1 bankAddress2 bankAddress3 bankCountry iban bban bbaN2 bbaN3 bic creditorId   Expose branch Payment settings tab in Branch endpoints The Branch APIs have been changed and the expandBanksettings parameter can be set to get Bank information from the branches. The following columns on the tab Payment settings will be returned: bankName bankAddress1 bankAddress2 bankAddress3 bankCountry iban bban bbaN2 bbaN3 bic creditorId   Wrong status when updating the sales order where the customer has exceeded its credit limit Earlier, when a customer had exceeded its credit limit and when you updated a sales order using PUT /api/v1/salesorder/{salesorderNumber} from status "Hold", the status didn't change to "Credit hold". Instead, it changed to "Open". This has now been fixed, so it works exactly as in the user interface.   ... View more