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.31.0 version has been planned as 21/12/2020 Release plan & date may vary. We will keep you informed of any changes. Release Notes. Documentation Errors in the response returned from the ProjectTransaction endpoint In previous versions, the ProjectTransaction endpoint was not showing in the response message the CreditAccountGroup for the GET operation. Now this issue has been fixed.   ... View more

Release Notes. Documentation Set another max. page size for GeneralLedgerTransaction and Balance endpoints Previously, the MaxPageSize setting was common for the entire API. We were not able to change it just for a certain endpoint. Because the general ledger endpoints export a big amount of data, sometimes we want to increase the MaxPageSize only for those endpoints to speed up the data transfer. Now we introduced an individual MaxpageSize setting for GeneralLedgerTransactions, GeneralLedgerBalanceV2 and JournalTransactionV2 Unable to update fields in a released Sales Invoices(Debit note) via API Earlier, there were some fields in the debit note that could not be updated via API (PUT api/v1/customerDebitNote/{debitNoteNumber}), after the debit note was released. This has now been fixed. (cashDiscountDate, documentDueDate, paymentMethodId and cashAccount) PUT Inventory returns "tstamp cannot be empty" Earlier, the PUT/api/v1/inventory method sometimes returned an error message regarding tstamp, when item classes had 'Replenishment settings' added. This has now been fixed. Purchase invoices with a leading space in the reference number Previously, it was possible to create purchase invoices with a leading space in the reference number using manual numbering, and that caused data corruption. This has now been fixed. Unable to update fields in the released Sales invoices (AR301000) window via API Earlier, some fields in the Sales invoices (AR301000) window could not be updated through the API, after the invoice was released. This has now been fixed, so that the fields "documentDueDate", "cashDiscountDate", "paymentMethod" and "cashAccount" are updated when using the PUT method for the customerInvoice API. 8.30.0 of Visma.net ERP version was a zero downtime deployment. Users were able to continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment have been notified about the possibility to move to the new version. ... View more

Release date for 8.30.0 version has been planned as 15/12/2020 Release plan & date may vary. We will keep you informed of any changes. Version 8.30.0 of Visma.net ERP will be deployed at 20:00 CET Users can continue working in the system during the upgrade. The ones that are actively using the system will be notified about the possibility to move to a newer version.   Release Notes. Documentation Purchase invoices with a leading space in the reference number Previously, it was possible to create purchase invoices with a leading space in the reference number using manual numbering, and that caused data corruption. This has now been fixed. Unable to update fields in a released Sales Invoices(Debit note) via API Earlier, there were some fields in the debit note that could not be updated via API (PUT api/v1/customerDebitNote/{debitNoteNumber}), after the debit note was released. This has now been fixed. (cashDiscountDate, documentDueDate, paymentMethodId and cashAccount) Set another max. page size for GeneralLedgerTransaction and Balance endpoints Previously, the MaxPageSize setting was common for the entire API. We were not able to change it just for a certain endpoint. Because the general ledger endpoints export a big amount of data, sometimes we want to increase the MaxPageSize only for those endpoints to speed up the data transfer. Now we introduced an individual MaxpageSize setting for GeneralLedgerTransactions, GeneralLedgerBalanceV2 and JournalTransactionV2 Unable to update fields in the released Sales invoices (AR301000) window via API Earlier, some fields in the Sales invoices (AR301000) window could not be updated through the API, after the invoice was released. This has now been fixed, so that the fields "documentDueDate", "cashDiscountDate", "paymentMethod" and "cashAccount" are updated when using the PUT method for the customerInvoice API. PUT Inventory returns "tstamp" cannot be empty" Earlier, the PUT/api/v1/inventory method sometimes returned an error message regarding "tstamp", when item classes had 'Replenishment settings' added. This has now been fixed. ... View more

  Release Notes. Documentation Get all projects in the Project endpoint  In the previous version, when using the Project endpoint, it was not possible to get all projects and the response message showed error. This has now been fixed.   The release has been successfully deployed. 8.29.3 of Visma.net ERP version was a zero downtime deployment. Users were able to continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment have been notified about the possibility to move to the new version. ... View more

Release date for 8.29.3 version has been planned as 10/12/2020 - 17:00 CET Release plan & date may vary. We will keep you informed of any changes. 8.29.3 of Visma.net ERP version will be no downtime release. Users can continue working in the system during the upgrade. The ones that are logged in and using the system during the deployment will be notified about the possibility to move to a newer version. Release Notes Documentation Get all projects in the Project endpoint  In the previous version, when using the Project endpoint, it was not possible to get all projects and the response message showed error. This has now been fixed.   ... View more

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.29 version has been planned as 01/12/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/z6mvtpksxmcz   Release Notes. Documentation Improved error message on Project endpoint when wrong employeeID is selected Error handling for the Project endpoint on the PUT operation has been improved. When trying to change an existing project, by adding a wrong employee, the error shows message "400 Bad request 'EmployeeID' is not found". GET operation for Currency Endpoint (texchangerates/toCurrencyId/effectiveDate) does not return all the data shown in the swagger documentation In previous versions, the GET /api/v1/currency/exchangerates/{toCurrencyId}/{effectiveDate} endpoint did not return all data listed in the Swagger documentation. This has now been fixed. The ARInvoice query suffers from async network I/O Improved performance for GET CustomerInvoice, CustomerCreditNote and CustomerDebetNote endpoints by a using a smarter and more performance optimized SQL query. The CustomerInvoice endpoint allows leading spaces in the "referenceNumber" field via API POST Earlier, leading spaces were allowed in the CustomerInvoice endpoint for the field "referenceNumber" when performing a POST operation. This has now been fixed, so that CustomerInvoice, CustomerDebitNote and CustomerCreditNote endpoints will skip leading and trailing spaces in the "referenceNumber" field for the POST method. When "referenceNumber" contains spaces the response will be: "400 - Bad request, Error creating document. New document must have a number that can not contain spaces". Failing Swagger 3.0 rules in O2C API endpoints In Visma.net ERP, a swagger json document is currenctly exposed for our APIs that previously failed to Open API/Swagger 3.x rules. Earlier, one of the rules that failed was about Routes (path templates). Routes are supposed to be equal, but they were not due to the path variables being used. The resulting swagger json document ended up with having two distinct entries for the two path variables, instead of one. This has now been fixed and corrected all route attributes that had this problem have been corrected. $Batch Endpoint returns 401 - Unauthorized for all requests except first operation in the batch payload Earlier, $Batch Endpoint was returning 401-Unauthorized for all requests except first operation in the batch payload. This has now been fixed.   ... View more

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 Timecard 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. ... View more

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. ... View more

Release Notes. Documentation Underscore "_" character not allowed in Supplier endpoint records The Supplier endpoint has been updated so that it is no longer possible to create a supplier with a supplier number that contains the underscore "_" character. Wrong report format returned by the PrintShipmentConfirmation endpoint Earlier, a wrong report format was returned by the PrintShipmentConfirmation endpoint via API. This has now been fixed. The Customer endpoint allows leading and trailing spaces in the Number field via API POST Earlier, the Customer endpoint allowed both leading and trailing spaces in the Number field via API POST. This has now been fixed so that leading and trailing spaces are removed from the Number field and they will not lead to invalid data anymore. The Inventory endpoint allows leading and trailing spaces in the InventoryNumber field via API POST Earlier, the Inventory endpoint allowed both leading and trailing spaces in the InventoryNumber field via API POST. This has now been fixed so that leading and trailing spaces are removed from the InventoryNumber field and they will not lead to invalid data anymore. The Inventory endpoint POST allows creating stock items with underscore Earlier, it was allowed to create stock items with the underscore character (_) when using the Inventory endpoint POST. This is not allowed anymore and the validation is now the same as in the UI of Visma.net ERP. The Customer endpoint POST allows creating records with the underscore character (_) Earlier, the Customer endpoint POST allowed creating records with the underscore character (_) in the "number" field. This is now fixed, so that you will get a response back that you have used an invalid character. Supplier numbers with leading or trailing spaces not allowed in Supplier endpoint The Supplier endpoint has been updated so that it is no longer possible to create a supplier with a supplier number that has leading or trailing spaces. ... View more

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.27 version has been planned as 17/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/tnpcfmqbk6r4 Release Notes. Documentation Underscore "_" character not allowed in Supplier endpoint records The Supplier endpoint has been updated so that it is no longer possible to create a supplier with a supplier number that contains the underscore "_" character. Wrong report format returned by the PrintShipmentConfirmation endpoint Earlier, a wrong report format was returned by the PrintShipmentConfirmation endpoint via API. This has now been fixed. The Customer endpoint allows leading and trailing spaces in the Number field via API POST Earlier, the Customer endpoint allowed both leading and trailing spaces in the Number field via API POST. This has now been fixed so that leading and trailing spaces are removed from the Number field and they will not lead to invalid data any more. The Inventory endpoint allows leading and trailing spaces in the InventoryNumber field via API POST Earlier, the Inventory endpoint allowed both leading and trailing spaces in the InventoryNumber field via API POST. This has now been fixed so that leading and trailing spaces are removed from the InventoryNumber field, and they will not lead to invalid data any more. Supplier numbers with leading or trailing spaces not allowed in Supplier endpoint The Supplier endpoint has been updated so that it is no longer possible to create a supplier with a supplier number that has leading or trailing spaces. The Inventory endpoint POST allows creating stock items with underscore Earlier, it was allowed to create stock items with the underscore character (_) when using the Inventory endpoint POST. This is not allowed any more and the validation is now the same as in the UI of Visma.net ERP. The Customer endpoint POST allows creating records with the underscore character (_) Earlier, the Customer endpoint POST allowed creating records with the underscore character (_) in the "number" field. This is now fixed, so that you will get a response back that you have used an invalid character. ... View more