Release date for 8.63.0 version has been planned as 31/08/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 Additional fields included in Employee endpoint on GET operations There are new fields: Employee class, Branch, Calendar, Employee login, and Work group ID available on the Employee endpoint for the following operations: - GET /api/v1/employee/{employeeCd} - GET /api/v1/employee "createdDateTime" and "createdDateTimeCondition" not working via GET CustomerInvoice and CustomerCreditNote endpoints Earlier, the parameters "createdDateTime" and "createdDateTimeCondition" were not working via the GET CustomerInvoice and CustomerCreditNote endpoints. This has now been fixed. DiscountAmount omitted when posting to V2/CustomerInvoice after version 8.56 Earlier, the option Manual discount on sales Invoice lines (AR301000) was not set correctly when posting to the V2/CustomerInvoice endpoint. This has now been fixed.     Due dates for breaking changes: First announcement: Visma.net Financials API updates for version 8.61.0 (August 2021) 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 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. Nov16, 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 date for 8.60.0 version has been planned as 10/08/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 Deprecated PUT, POST and GET v1/currency/ExchangeRates methods The PUT, POST and GET v1/currency/ExchangeRates methods are deprecated and will be removed on November 16th 2021. Start using the new methods under v2/currencyRate. New Parameters/Flags to improve the performance of the General Ledger Transactions Endpoint Parameters to avoid additional data for Account, Branch and beginning and ending balance in the query has been added to improve the performance for this API ExpandAccountInfo: By default, if no value is provided, True and each transaction returned will include extended information about the account. If False, the account information will include only Number, Description, Type and GlConsolAccountCD. ExpandBranchInfo: By default, if no value is provided, True and each transaction returned will include extended information about Branch (number and name). If False, the branch information will include only the branch number. IncludeTransactionBalance By default, if no value is provided, True and each transaction returned will include its balance. If False, the transactions returned will not include their balances (fields BegBalance, EndingBalance, CurrBegBalance, CurrEndingBalance) Pagination and filtering issues introduced with performance improvement of GET salesorderbasic endpoint in 8.59 In 8.59 we introduced a performance optimization for GET salesorderbasic endpoint which resulted in some issues with pagination and filtering. This has now been fixed, and we have reactivated the optimization again. GET SalesOrder endpoint returns an internal project ID in project Earlier the GET SalesOrder endpoint returned and internal ID in project. This has now been fixed by adding property ProjectCD containing the visible ID for the project. Enabling integrations to utilize this value. A new easier method to use the Currency endpoint   The currency endpoints have been changed and a new version 2 added for Exchange rate and Rate type.   GET api/v1/currency and GET /api/v1/currency/{curyId} has been extended with new columns     "symbol": "string",     "isBaseCurrency": true, - is only returned on the currency that is the base currency.     "decimalPrecision": 0,     "isUsedForAccounting": true New version 2 of Currency rates GET /api/v2/currencyrate with parameter fromDate toDate fromCurrency toCurrency rateType Returning     "id": 0,     "fromCurrencyId": "string",     "toCurrencyId": "string",     "rateType": "string",     "rate": 0,     "effectiveDate": "2021-08-04T00:00:00",     "multDiv": "string",     "rateReciprocal": 0 For POST, the CurrencyRateID is removed as parameter and From and To Currency is part of the request. POST /api/v2/currencyrate   "fromCurrencyId": "string"   "toCurrencyId": "string"   "rateType": "string"   "effectiveDate": "2021-08-04"   "rate": 0   "multDiv": "Multiply" For PUT, the request only contain Rate and MultiDiv to avoid updating an existing Rate for a other currency/ratetype by mistake. PUT /api/v2/currencyrate with parameter currencyRateId   "rate": 0   "multDiv": "Multiply" New API's for Currency rate type: GET /api/v2/currencyratetype     "id": "string",     "description": "string",     "daysEffective": 0 POST /api/v2/currencyratetype   "id": "string"   "description": "string"   "daysEffective": 0 ... View more

Release Notes Documentation Linear degraded performance from GET salesorderbasic endpoint when increasing page number using pagination Previously, when you called the GET Salesorderbasic endpoint, its performance linearly degraded when increasing the pageNumber parameter. This has now been fixed, in addition to a generic performance improvement of ~25% showed on our test company (the effect of this depends on the number of sales order documents and lines in the system). Project validation when using "cashTansaction endpoint" for creating "cash transactions" with "projects" and "accounts" not included in the "account groups" In previous versions, you were able to create cash transactions with projects on accounts that are not included in account groups using the CashTransaction endpoint. This issue has been fixed by adding validation on project, which checks if the account is included in an account group or not. ... View more

Release date for 8.59.0 version has been planned as 03/08/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 Linear degraded performance from GET salesorderbasic endpoint when increasing page number using pagination Previously, when you called the GET Salesorderbasic endpoint, its performance linearly degraded when increasing the pageNumber parameter. This has now been fixed, in addition to a generic performance improvement of ~25% showed on our test company (the effect of this depends on the number of sales order documents and lines in the system). Project validation when using cashTansaction endpoint for creating cash transactions with projects and accounts not included in account groups In previous versions, you were able to create cash transactions with projects on accounts that are not included in account groups using the CashTransaction endpoint. This issue has been fixed by adding validation on project, which checks if the account is included in an account group or not. ... View more

Release Notes Documentation Ungraceful error message thrown when client attempts to POST Customer Invoice V2 Earlier when you did a post to api/v2/customerinvoice containing origInvoiceDate with Use Value Date not active in the Accounts Receivable Preferences (AR101000) you did not get a clear error message. This has now been fixed, and you will get a clear error message in the response explaining why it failed. The error message will not contain the invoice number, since the invoice is not yet created when the error occurs. ... View more

Release date for 8.58.0 version has been planned as 27/07/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 Ungraceful error message thrown when client attempts to POST Customer Invoice V2 Earlier when you did a post to api/v2/customerinvoice containing origInvoiceDate with field disabled in the Accounts Receivable Preferences (AR101000) you did not get a clear error message. This has now been fixed, and you will get a clear error message in the response explaining why it failed. The error message will not contain the invoice number, since the invoice is not yet created when the error occurs. ... View more

Release Notes Documentation GET "inventory" returns "warehouseID" with trailing spaces In some scenarios, GET "inventory" endpoint returned trailing spaces for warehouse id under warehouseDetails, which led to DTO property could not be used directly in other API endpoints. This has now been resolved. ... View more

Release date for 8.57.0 version has been planned as 20/07/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 "inventory" returns "warehouseID" with trailing spaces In some scenarios, GET "inventory" endpoint returned trailing spaces for warehouse id under warehouseDetails, which led to DTO property could not be used directly in other API endpoints. This has now been resolved. ... View more

Release date for 8.56.0 version has been planned as 13/07/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 Pagination parameters wrongfully introduced for VatCatergory Endpoint in swagger documentation Even though the 'VatCategory' endpoint does not support pagination, the 'PageSize' and 'PageNumber' parameters were exposed in Swagger documentation. Now they have been removed. Posting "CustomerInvoice/V2" and changing the date via the UI resets Unit price on lines Earlier, when using "POST V2/CustomerInvoice" and changing the invoice date via the UI, the Unit price was reset on the invoice lines. This has now been fixed. GET warehouse endpoint returning trailing spaces in several IDs Earlier, the GET warehouse endpoint returned receiptLocationId, shipLocationId, returnLocationId, locations-locationId, and dropShipLocationId with trailing spaces. This has now been fixed, and IDs will not contain trailing spaces in the response any more. Wrong documentation in the GET Supplier Invoice Endpoint for "Released" parameter Earlier, the documentation for the "Released" parameter available in the GET Supplier Invoice endpoint was incorrect. The issue has now been fixed. Wrong account in credit note lines when created with API function Reverse and Apply to note Earlier, a wrong account was generated in the lines of credit notes when they were created using api/v1/customerinvoice/{invoiceNumber}/action/reverseandapplytonote endpoint. This has now been fixed. KitSpecification endpoint missing LastModifiedDateTime in the DTO and cannot be filtered upon Earlier, GET KitSpecification endpoint was missing the field LastModifiedDateTime in the DTO and could not be filtered upon. This has now been fixed. ... View more