We have deployed a new version of the Sales Order Service API to production containing under the hood stuff to improve the quality and prepare for the future.   Release notes Description HasManualPrice property exposed in GET /salesorders/{type}/{id}/lines endpoint We added HasManualPrice property to the line in GET /salesorders/{type}/{id}/lines endpoint. This field indicates if the unit price of the line has been added manually or by the system. 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. ... Vis flere

We have deployed a new version of the Sales Order Service API to production containing under the hood stuff to improve the quality and prepare for the future.   Release notes Description freightCost and freightTotal added to the SalesOrderDto Freight properties freightCost and freightTotal has been added to the SalesOrderDto/totals.   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. ... Vis flere

We deployed a new version of the Sales Order Service API to production. Version contains some under the hood stuff in addition to this:   Release Notes Description Use Export type on customer location to set tax category Previously the Tax category for an order line was selected based on the Export type of the customer class. This is not changed so that first we check the Export type on the customer location to set the Tax category. If the Export type on customer location is not set, the selection of the Tax Category is based on the Export type on the customer class.   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. ... Vis flere

Yesterday we deployed a new version of the Sales Order Service API to production.   Release Notes Description Support for use of Replacement cost We have now implemented support for setting the replacement cost of a line, which is based on the supplier price, suppliers last cost and items last cost. Replacement cost is set by the system and by using the useReplacementCostForProfitAndMargin option, one can determine which cost to use in the margin and profit and total cost calculations for the order. With the option activated the replacement cost of the order lines are used and with the option off the unit cost of the lines are used. Support for Profit and margin We now implemented support for setting the unit cost of a line. Unit cost can be set in POST, else it is set automatically by the system. Unit cost is also included in GET. With the unit cost set for the order line(s), the total cost of the order and the margin and profit of an order will now be set for orders created from the API. To use the unit cost of the lines for the total cost of the order, the option 'useReplacementCostForMarginAndProfit' should be false.   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. ... Vis flere

We deployed a new version of Sales Order Service API to production yesterday.   Release Notes Description Improve performance when posting sales order with a large number of lines We have improved the response time when posting new sales orders, especially when including a lot of lines with the request. The specific problem was related to looking up and assigning subaccounts to sales order lines. ... Vis flere

We deployed a new version of Sales Order Service API to production earlier today containing a few smaller improvements.   Release Notes Description Unit cost set when quantity on hand is 0 We have implemented a change so that the unit cost for a row is set correctly when the quantity on hand is 0. In addition we have also added a fallback to set the unit cost is warehouse is not set in the line(in this case we use the default warehouse set on the item). Upgrade libraries to .NET 6.0.3 We have upgraded libraries to the latest .NET 6.0.3 March 2022 update. Unit price not calculated correctly Previously the unit price was not calculated correctly when a order had a different currency than the base currency and the unit price was taken from the default price of the item. This has now been fixed. Unbilled and Unshipped total amounts not set correctly Previously when a order contained rows with different operation the Unbilled and Unshipped total amounts were not calculated correctly. This has now been fixed. ... Vis flere

Yesterday we deployed a new version of the Sales Order Service API to production. This version contains under the hood stuff for the near future, and should not have any effect on existing integrations. ... Vis flere