Because of an error, the release notes during the period May - August 2024 were not automatically posted. Here are the release notes for this period.   Release notes Description LOT/Serial numbers available in GET/Inventory It is now possible to expand LOT/serial in GET/Inventory endpoint. If you use expand=lotSerial without expand=location, it will show the Lot/serial for item on Warehouse level If you use expand=lotSerial and expand=location, it will show the Lot/serial for item on Warehouse location level Only Lot/Serial numbers that has a quantity will be included in the response Access to order in interactive API now restricted based on user's access to branch For the POST and PATCH endpoints, if a call is done with a user token for a user without access to the order's branch, the endpoint will now return a 404 error. POST/SalesOrders/Lines extended with sortOrder You can now in POST/SalesOrder/lines set the sortorder for the added line(s). If not provided, the new line(s) will be added last and if providing sort order that already exist, the lines with higher sort order value will get increased sort order. "isRotRutDeductable" removed from GET/api/v3/SalesOrders/{type}/{orderId} "isRotRutDeductable" is now, as announced previously, removed from GET/api/v3/SalesOrders/{type}/{orderId}. You use the field "isRotRutDeductible" instead. "appartment" removed from GET "appartment" is now, as announced previously, removed from GET/api/v3/SalesOrders/{type}/{orderId}/rotrut. You use the field "apartment" instead. Input for sortOrder in PATCH/SalesOrders/lines It is now possible to set sortOrder to a value higher than the line count of the order. Previously this was not possible and you received an error. Access to order in interactive API now restricted based on user's access to branch For the GET endpoints, if a call is done with a user token for a user without access to the order's branch, the endpoint will now return a 404 error. PurchaseOrderSource set according to warehouse Earlier, after changing the warehouse on a line, purchaseOrderSource was not updated according to the warehouse. This has now been fixed. Supplier not found or is not active error From now, when the supplier number contain leading or trailing spaces in the id, there will be no error message. Validation for supplierId Now it is no longer needed that purchase order source is set to be able to set the supplier ID for the order line Status added in GET/shipment The shipment status field is now included in the GET/shipment endpoint Orders created via the new Sales order service now included in classic menu search Orders created via the new Sales order service (API and UI) are no longer missing from the classic menu search results under Transactions and registers. Validation of warehouse location for receipt lines When adding a order line with operation: "Receipt", and the warehouse location do not allow receipts, you will get an error. Projects restricted to customer If you have restricted projects based on customer in the Project preferences (PM101000) window, and you set a project for an order, you will now get a 400 error if the project is not connected to the order's customer. ... View more

Due to an issue with the automatic release notes to the Community starting from 28th of September 2023 I'm posting the release notes for this time period manually.   Release notes Description Support for setting status to Open Setting the order status to Open is now supported, for example, when the current status is Cancelled. ... View more

Due to an issue with the automatic release notes to the Community starting from 28th of September 2023 I'm posting the release notes for this time period manually.   Release notes Description Supplier price not set correctly When the supplier on an order line differs from the line item's default supplier, the supplier price is no longer set incorrectly. purchaseOrderId field is available in GET/lines and GET /lines/{lineId} The purchaseOrderId field is now available in GET/lines and GET /lines/{lineId}. This field displays the purchase order number that is linked to the sales order line. Support for multi-language If multi-language is set up in the system, the description of the order line and inventory item is now set according to the language of the customer. ... View more

Due to an issue with the automatic release notes to the Community starting from 28th of September 2023 I'm posting the release notes for this time period manually.   Release notes Description Filter Inventory endpoint with LastModifiedDate It is now possible to filter the Inventory endpoint with the LastModifiedDateTime value Support for Completed in order line Setting the Completed field in order lines is now supported. Line replacement unit cost converted to order currency Earlier, the line replacement unit cost was not converted to the currency of the order, but the base currency was used instead. This has now been fixed. Support for cancelling an order You can now cancel an order by changing the status of an order to Cancelled. Note that, when you set an order to Cancelled, you cannot update any more fields. Support for Attachment information in GET order and GET order lines You can now get information about the attachments that have been added to an order or order lines via GET Order and GET order lines. ... View more

We have now released the functionality in Sales Order Service API for supporting setting salesperson in header and sales person and commissionable in order line. Based on the sales person set on the line, we now also calculate the commissions for the order. ... View more

We have an early Christmas gift for you! We have now released new endpoints in the Visma.net ERP Sales Order API for deleting order and order lines:   DELETE/api/v3/SalesOrders/{type}/{orderId} - Delete an existing order DELETE/api/v3/SalesOrders/{type}/{orderId}/lines - Delete lines form existing order   In the near future we will also release endpoints for updating(PATCH) order and order lines & adding lines to existing orders(POST)   Please view the following post for additional information on the API: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Merry Christmas & Happy New Year! ... View more

Release Notes Documentation Subaccount error when POSTing order Previously, you got an error when creating an order and the default subaccount of the order line contained a segment with empty segment value. This is now fixed.   If you are new to the neXtGen services, please look at the Getting started with the first neXtGen service: Visma.net ERP Sales Order API for an introduction. ... View more