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

As announced previous, the original plan was to close specific sales order endpoints in v1 and v2 by 1st of June 2023. This due date is now changed. We plan to be functional complete with Sales order API v3 by Q2-2024(30th of June 2024), thus new Due date being end of Q4-2024(31st of December 2024). If any change would occur for this, we will announce that as soon as possible.   The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html ... View more

Hi   As part of the implementation of the Sales order API v3 we update the Inventory quantities(Available, Available for shipping etc) for the items included in the sales order.   While testing this, we noticed concurrency issues for the quantities when orders with the same item are created at the same time, which can lead to wrong quantities and/or longer time for processing the order.   To improve the flow, we plan to introduce eventual consistency related to the inventory update for the orders created from the Sales order API v3. This means that the quantities will still be updated, but the update will run as a separate process in the background right after the order is created.   For you as an integrator, the only difference from today is that the inventory quantities will be updated within a time frame of 100 - 3000 ms. This will be seen, for example, in that the quantities in GET/inventory will be updated within that time frame.   Therefore we want to ask you, our integrators, about your view on this. Is it OK that the inventory quantities are updated with this short delay? Please comment your input in this thread. ... View more

Hi   We have an issue in Visma.net ERP Sales order API v3, where when creating an order the 'Available' and 'Available for shipping' quantities are not updated correctly for the item(s). We are now implementing fix for this and will let you know when the problem is solved.   To get the quantities corrected, one can open the UI and select Inventory - Processes - Validate inventory(ScreenID: IN505000) and run the process, this will recalculate the quantities. ... View more

Question We received a 400 Bad Request when using POST/api/v3/SalesOrders. How can I see what is the reason for this error? Answer When receiving a 400 Bad Request it include an error response body. This response body will indicate the reason for getting the error, looking like this:     ... View more

We are really excited to announce that we have now released the new and highly requested endpoints PATCH and POST in the Visma.net Sales Order API v3.   We are looking forward to your input and feedback. PATCH Create modifications/updates to an existing sales order: PATCH/api/v3/SalesOrders/{type}/{orderId}   Create modifications/updates to an existing sales order line: PATCH/api/v3/SalesOrders/{type}/{orderId}/lines  POST Add new line(s) to an existing sales order: POST/api/v3/SalesOrders/{type}/{orderId}/lines   Authentication Please note that it is possible to authenticate “old” api integrations with Visma Connect. Since Sales Order API v3 only supports authentication via Visma Connect, this will make it easier to use resources/endpoints from both APIs.    For example, you want to know which inventory items you can add to a sales order, because you are using the same authentication you can easily get the Inventory information from the "old" api integration.   For more information about Visma Connect authentication, please read: https://community.visma.com/t5/Knowledge-base-in-Developers/Guide-Move-from-VNI-to-Visma-Connect-Authentication-for-Visma/ta-p/542146   Getting  started How to get started with the Sales Order API v3, plus additional information, please see: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436   ... 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

Viikonlopun versiopäivityksen jälkeen on ilmennyt virhe missä rivin/tapahtuman käsittelyssä tulee virhe 'TaxCalcMode ei saa olla tyhjä'. Tämä on todettu virheeksi ja on tuotekehityksen korjattavana. Rivin/tapahtuman saa piilotettu seuraavasti kunnes tämä on korjattu:   1. Valitse ko. rivi ja avaa Muodosta tapahtumat-välilehti ja laita ruksi kohtaan Muodosta 2. Klikkaa Tallenna 3. Tämän jälkeen pääsee piilottamaan tai suorittaamaan riviä ... View more

Kysymys: Eräpäivärajauksen mukaan lasku pitäisi nousta mukaan maksatukseen Käsittele maksut-ikkunassa, mutta jostain syystä se ei ole valittavana.   Ratkaisu: Määritä Maksupäivä-suodatin samaksi päiväksi kuin Eräpäivä-suodatin. Voit myös jättää Eräpäivä-kenttä tyhjäksi ja Maksupäivä-kentässä valita päivämäärä mihin asti haluat laskut maksaa.     ... View more

Liitteenä olevassa ohjeessa käydään läpi Hankintakulukoodien määritykset ja esimerkkejä hankintakulukoodien käytöstä. ... View more