Release date for 8.75.0 version has been planned as 29/11/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 Branch filter is now correctly applied for Budget endpoint When using GET for Budget, the mandatory Branch parameter was not used correctly for filtering. This has now been fixed. PUT Stocktake endpoint (v2-version) not generating value on variance cost Earlier, the v2-version of the PUT Stocktake endpoint did not update variance cost, neither on header nor lines. Also delete stocktake line from UI did not recalculate header totals. This has now been fixed. CustomerPayments: Returns 500 results even when pageSize is set to 1000 Earlier, the maximum page size was hard coded to 500 and so the response for the GET customerPayment endpoint was able to return up to 500 payments. This has now been changed so that the maximum page size is configurable, and the value is taken from the web.config file for every GET endpoint with the maxpageSize filter. GET CustomerInvoice endpoint using filter "dunningLevel" parameter returns an empty result Earlier, the GET CustomerInvoice endpoint using some filters returned an empty result. This has now been fixed so that the endpoint returns an empty array instead of an empty result.   Due dates for breaking changes Release Notes Documentation Due 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 February 28th 2022. Start using the new methods:  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment  - POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber} /attachment Feb 28, 2022 Breaking change on Currency endpoint The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on January 11th, 2022. Start using the new methods under v2/currencyRate. Jan 11, 2022 Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Jan 18, 2022   ... View more

Release date for 8.74.0 version has been planned as 16/11/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 Changes on GeneralLedgerTransactions endpoint parameters To improve the performance of GeneralLedgerTransactions endpoint, the three new flags that were introduced in version 8.60 and that allow users to retrieve extended data if necessary (expandBranchInfo, expandAccountInfo, includeTransactionBalance) are now set to false by default. Please verify swagger documentation and if you consider the extended data is necessary, set the flags to True for your calls. Posting of attachments to JournalTransactionV2 for all modules  Now it's possible to use the new POST /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/attachment and /api/v2/journaltransaction/module/{module}/{journalTransactionNumber}/{lineNumber} /attachment to add attachments for transactions created for all workspaces. Earlier, it was only possible to add attachments for transactions created in the general ledger (GL) workspace. The old endpoints are set to obsolete but will be available for 6 months. Note that it's still only possible to post journal transactions for the workspace GL but when journal transactions for other workspaces are created from other modules and endpoints and ends up in journal transactions, so that the journalTransactionNumber exist, then it's now possible to add the attachment. Improved performance of GET journaltransaction When using GET /api/v2/journaltransaction with a lot of data, the calls became slower for each paginated call and could in some cases end up in a timeout. This has now been improved. Wrong sales account used in POST CustomerInvoice for export type customers Earlier, the POST CustomerInvoice endpoint gave an incorrect sales account on invoice lines for customers registered for export to EU or non-EU countries. This has now been fixed. Last modified date as UTC in the Branch endpoint When using GET for a branch or range of branches, the "lastModifiedDateTime" is now shown as UTC.   Due dates for breaking changes Release Notes Documentation Due Breaking change on Currency endpoint The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on January 11th, 2021. Start using the new methods under v2/currencyRate. Jan 11, 2022 Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Jan 18, 2022     ... View more

Release Notes Documentation Support correction of sales invoice by API endpoint  Correction of sales invoices by a new API endpoint POST customerinvoice/{SalesInvoiceNumber}/action/correct is now supported with same functionality as we have for this feature in the UI. There is now a new way of correcting invoices, which requires fewer steps to update/correct an invoice than the previous standard reversal process. You can find the "Correct invoice" feature under the Actions drop-down list button in the Sales invoices (AR301000) window. When using the "Correct invoice" feature, the system will automatically create a copy of the original invoice that can be further edited. In the background, when releasing this new invoice, the system will automatically create a sales credit note for the original invoice and will match it against the chosen invoice to be corrected. As a note the original invoice will remain in status Open until the new corrected document will be finally released, but will no further be included in the payment process. Correcting of invoices with lines from the Shipments (SO302000) or Sales orders (SO301000) windows is currently not supported. No webhook notification when sales invoice status changed to "Closed" Earlier, there was no webhook notification when the status of an invoice was changed to "Closed" in Visma.net ERP. This has now been fixed. ... View more

Release date for 8.73.0 version has been planned as 09/11/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 Support correction of sales invoice by API endpoint  Correction of sales invoices by a new API endpoint POST customerinvoice/{SalesInvoiceNumber}/action/correct is now supported with same functionality as we have for this feature in the UI. There is now a new way of correcting invoices, which requires fewer steps to update/correct an invoice than the previous standard reversal process. You can find the "Correct invoice" feature under the Actions drop-down list button in the Sales invoices (AR301000) window. When using the "Correct invoice" feature, the system will automatically create a copy of the original invoice that can be further edited. In the background, when releasing this new invoice, the system will automatically create a sales credit note for the original invoice and will match it against the chosen invoice to be corrected. As a note the original invoice will remain in status Open until the new corrected document will be finally released, but will not  be included in the payment process. Correcting of invoices with lines from the Shipments (SO302000) or Sales orders (SO301000) windows is currently not supported. No webhook notification when sales invoice status changed to "Closed" Earlier, there was no webhook notification when the status of an invoice was changed to "Closed" in Visma.net ERP. This has now been fixed.   Due dates for breaking changes First announcement: Visma.net Financials API updates for version 8.61.0 (August 2021) Release Notes Documentation Due Breaking change on Currency endpoint The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on January 11th, 2021. Start using the new methods under v2/currencyRate. Jan 11, 2021 Breaking change on GeneralLedgerTransactions To improve the performance of GeneralLedgerTransactions endpoint, there are now three new flags to allow users to retrieve extended data only if necessary: expandBranchInfo, expandAccountInfo, includeTransactionBalance. To ensure the API compatibility, the flags were set to True by default, but they will be switched to False by November 16th 2021. Please verify swagger documentation and if you consider the extended data is necessary, set the flags to True for your calls. Nov 16, 2021 Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Jan 18, 2022 ... View more

Release Notes Documentation Get discountCode endpoint representing wrong DTO format Earlier, the GET DiscountCode endpoint represented a wrong DTO format. This has now been fixed in version V2 of the endpoint. GET discount endpoint representing wrong DTO format Earlier, the GET discount endpoint represented a wrong DTO format. This has now been fixed in version V2 of the endpoint. Project and project task in output with GET for PO receipt Project and project task will now be in the output if you do GET for PO receipt. ... View more

Release date for 8.72.0 version has been planned as 02/11/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 Project and project task in output with GET for PO receipt Project and project task will now be in the output if you do GET for PO receipt. Get discountCode endpoint representing wrong DTO format Earlier, the GET DiscountCode endpoint represented a wrong DTO format. This has now been fixed in version V2 of the endpoint. GET discount endpoint representing wrong DTO format Earlier, the GET discount endpoint represented a wrong DTO format. This has now been fixed in version V2 of the endpoint.     Due dates for breaking changes First announcement: Visma.net Financials API updates for version 8.61.0 (August 2021) Release Notes Documentation Due Breaking change on Currency endpoint The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on January 11th, 2021. Start using the new methods under v2/currencyRate. Jan 11, 2021 Breaking change on GeneralLedgerTransactions To improve the performance of GeneralLedgerTransactions endpoint, there are now three new flags to allow users to retrieve extended data only if necessary: expandBranchInfo, expandAccountInfo, includeTransactionBalance. To ensure the API compatibility, the flags were set to True by default but they will be switched to False by November 16th 2021. Please verify swagger documentation and if you consider the extended data is necessary, set the flags to True for your calls. Nov 16, 2021 Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Jan 18, 2022 ... View more

Release Notes Documentation GET StocktakeV2 endpoint is missing "baseUnit" on lines Earlier, the GET Stocktake endpoint, in version V2, didn't return "baseUnit" for stocktake lines. This has now been fixed Support for webhook notification on delete shipment Previously webhook notification when deleting a shipment was not supported. We have now added DELETED support on shipment_changed notification. The makes it possible for integrations to be aware of when a shipment is deleted, and react upon such an event. Saleorders endpoint getting slower for each paginated call Earlier, the GET Salesorder endpoint got slower and slower for each paginated call. This has now been fixed. CashSale endpoint getting slower for each paginated call Earlier, the GET CashSale endpoint got slower and slower for each paginated call. This has now been fixed. GET SalesPerson endpoint giving wrong DTO format for pagenumber and pagesize Earlier, the GET SalesPerson endpoint gave a wrong DTO format for pagenumber and pagesize in response. This has now been fixed. POST operation for JournalTransactionV2 for non-existing and inactive branches corrected When using the POST operation for JournalTransactionV2 including a non-existing or inactive branch, it was posted to another branch. This has now been fixed and the request is rejected in these cases. Error on purchase receipt from API with allocation and same stock item twice Earlier, when creating a purchase receipt from API with the same stock item twice and with allocation, you got an error message. This has now been fixed. ... View more

Release date for 8.71.0 version has been planned as 26/10/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 GET StocktakeV2 endpoint is missing "baseUnit" on lines Earlier, the GET Stocktake endpoint, in version V2, didn't return "baseUnit" for stocktake lines. This has now been fixed Support for webhook notification on delete shipment Previously webhook notification when deleting a shipment was not supported. We have now added DELETED support on shipment_changed notification. The makes it possible for integrations to be aware of when a shipment is deleted, and react upon such an event. Saleorders endpoint getting slower for each paginated call Earlier, the GET Salesorder endpoint got slower and slower for each paginated call. This has now been fixed. CashSale endpoint getting slower for each paginated call Earlier, the GET CashSale endpoint got slower and slower for each paginated call. This has now been fixed. GET SalesPerson endpoint giving wrong DTO format for pagenumber and pagesize Earlier, the GET SalesPerson endpoint gave a wrong DTO format for pagenumber and pagesize in response. This has now been fixed. POST operation for JournalTransactionV2 for non-existing and inactive branches corrected When using the POST operation for JournalTransactionV2 including a non-existing or inactive branch, it was posted to another branch. This has now been fixed, and the request is rejected in these cases. Error on purchase receipt from API with allocation and same stock item twice Earlier, when creating a purchase receipt from API with the same stock item twice and with allocation, you got an error message. This has now been fixed.   Due dates for breaking changes First announcement: Visma.net Financials API updates for version 8.61.0 (August 2021) Release Notes Documentation Due Breaking change on Currency endpoint The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on November 23rd, 2021. Start using the new methods under v2/currencyRate. Nov 23, 2021 Breaking change on GeneralLedgerTransactions To improve the performance of GeneralLedgerTransactions endpoint, there are now three new flags to allow users to retrieve extended data only if necessary: expandBranchInfo, expandAccountInfo, includeTransactionBalance. To ensure the API compatibility, the flags were set to True by default, but they will be switched to False by November 16th 2021. Please verify swagger documentation and if you consider the extended data is necessary, set the flags to True for your calls. Nov 16, 2021 Breaking changes on Budget endpoint From January 18th 2022, the following breaking changes will be committed on GET method of the Budget endpoint:  - 'Branch' and 'Ledger' filters will become mandatory. Now they are specified to be mandatory by documentation, but it is not enforced by implementation.  - 'FinancialYear' filter will become mandatory  - Now, the branch filter requires being specified either by branch full name (example: BranchID - BranchName), either by branch ID surrounded by quotation marks. It will be simplified to require the branch ID without any other marks. Jan 18, 2022 ... View more

Release Notes Documentation New parameters "pageNumber" and "pageSize" in ExpenseClaim endpoint Two new parameters "pageNumber" and "pageSize" are now available in the ExpenseClaim endpoint. Also the Swagger documentation has been updated with the pagination enforcement notice. Swagger documentation on GET operation of Cash sales endpoint updated with pagination enforcement notice Swagger documentation on GET operation of Cash sales endpoint is updated with the pagination enforcement notice. Swagger documentation on GET operation of Employee endpoint updated with pagination enforcement notice Swagger documentation on GET operation of Employee endpoint is updated with the pagination enforcement notice. ... View more