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

A minor update (8.26.01) has been planned to be released for Visma.net ERP / API. Expected downtime for Visma.Net ERP & API (Nov 12, 22:30 CET - Nov 13, 00:30 CET / 2020) Status can be followed at: https://status.visma.com/incidents/mtxg450r71gp The following cases occurred in the 8.26 release are going to be fixed with this update. Visma.net ERP API: Summary Documentation V2/JournalTransactions: MetaData shows incorrect values since 8.26 update  In version 8.26.1 an error that returned wrong metadata (totalcount) in the API endpoint JournalTransactionV2 was fixed PurchaseReceipt shows different values for openQty in UI and via API Before when you did a GET request for purchase receipt and you had many receipt to one purchase then API call showed wrong amounts for orderqty, openqty, receiptqty. Now this bug is fixed.     Visma.net ERP:  Not possible to change the order of the lines on a SO. Earlier, it was not possible to rearrange the sales order lines. This resulted in missing lines on the order confirmation report. This has now been fixed, and historical data affected by this issue have also been resolved. Series id do not fill inn automatically in SO tab Discount details/Feilmelding ved valg av rabatt (mangler sekvens). In version 8.26 of Visma.net ERP, a bug was introduced where the Series ID of the Discount was not updated automatically when the Discount ID was added manually into a Sales order. This is has now been fixed.   For further information about ERP Patch details please contact Financials ERP / Community from your market. ... View more

Release Notes Documentation Increased max page size The default /max page size has been temporarily changed from 500 to 1000 for all endpoints where we have pagination and had max page size = 500. New operations for locations on Warehouse endpoint Two new operations have been implemented on the Warehouse endpoint: - POST operation of inventory locations which can be used by integrators for creating inventory locations on warehouses. - PUT operation of inventory locations which can be used by integrators for updating inventory locations on warehouses Change shipping term on purchase orders The field 'Shipping terms' has been added to the Shipping instructions tab of the Purchase orders window. This allows you to change the shipping term for each purchase order, if needed. The shipping term defined on the specific supplier is applied by default. Additionally, the Shipping terms field has been added to the Report designer and to the Purchase order endpoint. See the swagger documentation for additional information related to API. Beta tags removed for v2 endpoints and corresponding v1 endpoints marked as deprecated The following methods are marked as deprecated, and will be removed from May 2021: POST customerCreditNote, customerDebitNote and customerInvoice. The v2 of the same methods, optimized for performance, should now be used instead, and the beta tag for these have now been removed. API calls towards newly provisioned companies not updating user context Earlier, if you provisioned a new company and did API calls towards the newly provisioned company, you could end up on a node where the user context was not updated. This would typically give you a 500 internal server error and if you retried, it worked. The cache handling of user context has been improved so you should not end up in this scenario anymore. Read and create/update descriptions of multi-language supported fields via the API to support webshop and import of items From this version on, there is translation support via API for the Description field in the Stock items and Non-stock items windows with POST, PUT, GET specific translation, GET all translations for a stock item, and DELETE. The system now also supports retrieving a list of all supported languages via API, with information if a language is active and the default. Wrong error message on PurchaseReceipt endpoint when supplier is missing When the supplier was missing from the PurchaseReceipt endpoint, you got an error message saying that a customer number must be specified. Now the error message has been changed to "Error creating purchase receipt. New order must have a supplier number specified." Configuring of manual purchase invoice numbering series with API    The configuration of manual numbering for the Purchase invoice numbering series did not sync with API due to a cache issue. In fact, this issue affected all numbering sequences. This has been fixed in the 8.26 release. Purchase Receipt not inheriting currency from the supplier via POST API The Purchase Receipt POST operation did not inherit the currency from the supplier if the currency override setting was disabled. This has now been fixed. The reopenSalesOrder action is not working as expected via API Earlier, the reopenSalesOrder action did not work as expected via API. This has now been corrected, so that it works the same way as in the UI. Posting CustomerInvoice with CashAccount not belonging to the main branch causes issues Posting CustomerInvoice with CashAccount not belonging to the main branch caused issues after the 8.25 release. This has now been fixed. Sales order total gets the wrong total amount when using percentage discount Earlier, the Sales order total got the wrong total amount when using percentage discount via API. This has now been fixed. Invoices from Visma.net Project management get the wrong cash account Earlier, when branch information was used in an invoice, the payment method and the cash account used for the invoice were not set correctly according to how the payment method and the cash account were linked to the branch. This has now been fixed. ... View more