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 ... View more

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. ... View more

Release Notes Documentation Fix for PUT Stocktake V2 API request processing only the first 5 Lines We have resolved an issue caused by the "IsSqlUpdateOptimizationEnabled" feature flag in production environments. This issue limited the PUT Stocktake V2 request to processing only the first five update lines in a payload. The feature flag has now been fixed, and the PUT Stocktake V2 request processes all lines as expected     Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method As mentioned many times earlier, VNI authentication method had its End of life on 1st of June 2024. This is an urgent notice for all ISVs and partners with integrations in Visma.net: We have previously informed all partners and ISVs to migrate their existing integrations to Visma.net using the new authentication method through Connect. As from June 1st deadline is reached it is important to know that starting from the deadline, we will initiate throttling of these integrations. This means that we will start limiting the number of calls per hour per integration. During June we will gradually decrease the limit and allow less calls per hour. Additionally, starting mid-June, we will cease to issue new access tokens for these integrations. More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for-Visma-Connect/ba-p/542148 June 1, 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   ... View more

Release Notes Documentation As an ISV I want to get and update the note in purchaseReceipt-endpoints  There is now possible to havet the note for purchasereceipt, in header and lines, in the payload for create/update/read in the purchasereceipt endpoint.     API - Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method As mentioned many times earlier, VNI authentication method had its End of life on 1st of June 2024. This is an urgent notice for all ISVs and partners with integrations in Visma.net: We have previously informed all partners and ISVs to migrate their existing integrations to Visma.net using the new authentication method through Connect. As from June 1st deadline is reached it is important to know that starting from the deadline, we will initiate throttling of these integrations. This means that we will start limiting the number of calls per hour per integration. During June we will gradually decrease the limit and allow less calls per hour. Additionally, starting mid-June, we will cease to issue new access tokens for these integrations. More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for-Visma-Connect/ba-p/542148 June 1, 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 ... View more