Release Notes Documentation Introducing new filtering possilibities Introduce new filtering in the endpoints: GET v1/PurchaseOrder, GET v1/PurchaseOrderBasic ==> "orderDate", "deliveryDate" and "branch" . GET v1/shipment ==> "shipmentType" and "shipmentDate" GET v1/purchasereceipt, GET v2/purchasereceipt and GET v1/purchaseReceiptBasic ==> "receiptDate", "dueDate", "finPeriod" and "branch " Re-enabled behavior to edit an voided prebooking via API & UI When pre-booked document has been voided, now possible again to re-introduce and continue with this document as it would be an new document inserted. Available when updating an invoice line from the voided document. (UI or API) Functionality was temporarily disabled, while an issue was found impacting scenarios in combination of manually calculated VAT amounts, pre-booking, and split line. This has now been fixed.   API - Due dates for breaking changes Release Notes Documentation Due Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced in February 2025. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. 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 might 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 Sept   30,  2025   ... Skatīt vairāk

It is estimated that the new Base URL will be available by the end of February. Once it is released, a new date will be set 3 months after it becomes available. This means that the EOL date for the Base URL is currently set for 30.05.2025.   The original article has been updated with these new dates included. ... Skatīt vairāk

Release Notes Documentation GET SupplierInvoice call resulting in time-out The time-out experienced in the GET/SupplierInvoice responses was affecting companies with large subaccount registers. This has now been fixed.   POST v1/shipment/{shipmentNumber}/action/addLine return errormessage Earlier, POST v1/shipment/{shipmentNumber}/action/addLine did return errormessage like "Error: Another process has added SOOrderShipment. Your changes will be lost" in some circumstances. This has now been fixed.     API - Due dates for breaking changes   Planned removal of Sales Order API endpoints Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced in February 2025. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. 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 might 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 Sept 30, 2025 ... Skatīt vairāk

An API user has requested that the "Require Receipt" checkbox from IN202000 should be available through the inventory endpoint. ... Skatīt vairāk

An API user has requested that the "Require Receipt" checkbox from IN202000 should be available through the inventory endpoint. ... Skatīt vairāk

Release Notes Documentation New parameters included into supplier domains GET endpoints New parameters now available in the following endpoints: GET/controller/api/v1/supplierInvoice GET/controller/api/v1/supplierPayment GET/controller/api/v1/supplierdocument GET/controller/api/v1/supplier/{supplierNumber}/invoice GET/controller/api/v1/supplier/{supplierNumber}/document The new parameters which are now available: - paymentType (added for SupplierPayment) - Status (added for SupplierPayment) - Supplier (Added for SupplierInvoice & SupplierDocument) - Item (Added for all except SupplierPayment) - branch (Added for all) - financialPeriod (Added for all) - dueDate & dueDateCondition (Added for all) - docDate & docDateCondition (Added for all) - balance & balanceCondition (Added for all) Resolved: Incomplete GET Inventory API Response The Inventory API endpoint /controller/api/v1/Inventory previously returned only active items when no status parameter was specified. This has been resolved, and now all items, regardless of status, are returned as expected. Some API endpoints allow non-ascii characters in the LotSerialNbr field Previously, non-ascii characters were allowed in the lot-serial number field in the payload for POST/PUT purchaseReceipt- , POST/PUT salesOrder- and POST/PUT Shipment-endpoints. This has now been fixed     API - Due dates for breaking changes   Planned removal of Sales Order API endpoints We plan to be functionally complete by Q1-2025 (31st of March 2025), end of life date for the endpoints will be announced in February 2025. A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. 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 might 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 Sept 30, 2025 ... Skatīt vairāk

Due dates for breaking changes Release Notes Documentation Due Breaking change on Account endpoint - publicCode1 changes from int to nvarchar(20)  Due to legal changes required for the SAF-T report that are applicable January 1st 2025, the publicCode1 and publicCode2 fields will change type from int to nvarchar(20). The publicCode1 field is exposed on the Account endpoint, both on GET, PUT and POST. Nov 26, 2024 Planned removal of Sales Order API endpoints We plan to be functionally complete by Q4-2024 (31st of December 2024), thus new due date being end of Q1-2025(31st of March 2025). If any change would occur for this, we will announce that as soon as possible, A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. 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 Mar 31, 2025 ... Skatīt vairāk

Introduction In SalesOrder v1 and v2, when you set the {"markForPO": "true"}, the Purchase order source is by default set to Purchase to order. In SalesOrder v3, only the field purchaseOrderSource is included. If you set purchaseOrderSource in v3, markForPO will automatically be true in the database.   ScreenId=SO30100S   This change simplifies the process compared to v1 and v2, where you needed to include both markForPO and poSource if you wanted to set the Purchase order source to Drop-Ship. The change in v3 allows you to set Purchase order source with just one field.   Available Options for v3 There are two main methods to set the purchase order source in v3.   Option 1: Default Replenishment Setting in UI If an item has a default replenishment source, such as Drop Shipment or Purchase to Order, set in Item warehouse details screen (IN204500, Replenishment Info-tab), the system will automatically mark the line for PO when you add the item to an order line. The Purchase order source will be set according to the item's default setting.   ScreenId=IN204500   Option 2. Manual Setting If an item does not have a default replenishment source, set the Purchase order source manually for the line when needed. In v3, use {“purchaseOrderSource”: “purchaseToOrder” } instead of setting {markForPO: true} as in v1 and v2. See the documentation for more information.   POST /api/v3/SalesOrders   With these changes in v3, managing purchase order source in sales orders becomes more straightforward and efficient. ... Skatīt vairāk