Visma.net Financials API updates for version 8.72.0 (November 2021)

[#1]

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