Visma.net Financials API updates for version 8.28 (November 2020)

[#1]

This thread will be updated regularly up until the point of version-release.
If you have any questions & comments, please go to the case specific thread or post a new one to inform us about your inquiry in detail. You can also contact us via developersupport@visma.com

Release date for 8.28 version has been planned as 24/11/2020
Release plan & date may vary. We will keep you informed of any changes.

Maintenance status can be followed at : https://status.visma.com/incidents/jhz731q5flqb

Release Notes.	Documentation
Implementing Attachment feature for the ExpenseReceipt Endpoint (POST)	There is a new POST operation on the ExpenseReceipt endpoint "expenseReceipt/{receiptNumber}/attachment", which allows third party integrators to add attachments on expense receipts.
New POST operation exposed via the Timecard endpoint for "onHold" process	There is a new POST operation for the Time card endpoint "timeCard/{timeCardCd}/action/hold", which can be used by third party integrators to put a specific timecard On hold, which has been wrongly submitted by the user.
New filter "restrictedUser" for GET operations of some project API endpoints	There is a new filter "restrictedUser" for GET operation of the API endpoints Project, Project/tasks, Projectbasic and Projecttask, which can be used by third party integrators to identify the projects that are restricted to a specific ODP user ID.
Customer endpoint allows space in the "number" field	Earlier, it was allowed to use leading and trailing spaces in the "number" field of the Customer endpoint. This caused invalid data in the system. This has now been fixed, so that you will get an error message if spaces are being used: "400 Bad request - Error inserting the customer. Input data not valid. New customer must have a number that can not contain spaces."
VAT for FreightCost (Shipvia) is not calculated when posting a sales order via API	Earlier, the VAT for FreightCost (Shipvia) was not calculated when posting a sales order via API. This has now been fixed, so that freightCost (Shipvia) VAT is calculated when sending POST request via V1/V2 sales order endpoints.
Inventory endpoint allows space in the "inventoryNumber" field	Earlier, it was allowed to use spaces inside the "inventoryNumber" field of the Inventory endpoint. This caused invalid data in the system. This has now been fixed, so that you will get an error message if spaces are being used: "400 - Bad request, Error creating inventory. New inventory must have a number that can not contain spaces."
PUT "kitassembly" generates: Object reference not set to an instance of an object	Earlier, when you performed a PUT operation to the "kitassembly" endpoint, an error message was thrown: "Object reference not set to an instance of an object. " This has now been fixed.