Visma.net Financials API updates for version 8.63.0 (August 2021)

[#1]

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

[#2]

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