Release Notes Documentation Improvements in the GET Account API endpoints There are improvements in the GET Account API endpoints. Both, the 'Get a specific account' and the 'Get a range of accounts' endpoint will include values for: - Control account module - Allow manual entry - Public code - External code 1 - External code 2 - Analysis code in their responses. In addition, it is possible to set filters on - Public code - External code 1 - External code 2 - Analysis code in the 'Get a range of accounts' endpoint. GET v2/salesorder endpoint with use of pagination The GET v2/salesorder endpoint with the use of pagination no longer returns the error "Divide by zero error encountered". API - Due dates for breaking changes Release Notes Documentation Due Deprecated fields on Account endpoint The following fields are deprecated and will be removed on 13th of February 2024:  - ExternalCode1  - ExternalCode2  - AnalysisCode They should be replaced by fields: ExternalCode1Info, ExternalCode2Info, AnalisysCodeInfo, which contain more details. Feb 13, 2024 Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) 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 Dec 31, 2023 Planned removal of Sales Order API endpoints We plan to be functionally complete 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, 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 Dec 31, 2024 ... View more

  Release Notes Documentation POST api/v1/shipment/<shipmentnumber>/action/printshipmentconfirmation returns error message when using Visma Service API token Earlier, when using Visma Service API token, POST api/v1/shipment/<shipmentnumber>/action/printshipmentconfirmation returned "Error you do not have enough rights to access SO64200S". This has now been fixed. Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) 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 Dec 31, 2023 Planned removal of Sales Order API endpoints We plan to be functionally complete 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, 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 Dec 31, 2024 ... View more

Ready for the A(zure) Day We had the final Azure production test on Tuesday-Wednesday night. Some issues were reported during the test, which we have time to address before the migration. In general test was successful and we are ready for the migration weekend. The migration will be done during Oct 21, 2023 00:00 - Oct 23, 2023 08:00 CET. During Saturday, we will validate functionality and the plan is to be back online already during the weekend. This way we have some time to get feedback about possible issues before Monday morning. Note:  During this time, the Financials ERP, Financials ERP API and Sales Order Service API will not be available. The authorization/access tokens are not going to be affected by the migration.  The new IP address (NAT IP: 20.229.18.193) This Information might be needed for ISVs working with the FTP integration). For more information, please follow the status message: https://status.visma.com/incidents/3nplqy5y3syd ... View more

Release Notes Documentation PUT SupplierInvoice not allowing multiple SplitLines to be used (Affected specific companies - Feature used for API when restriction groups restricting default subaccount) When settings from General ledger account access (GL104000) were set to limit access towards accounts and subaccount segment, the update via PUT operation using SplitLines could not process the request. Restricted subaccount could not be processed when SplitLine was actioned more than once. This has now been fixed. The fix has been added under a feature toggle and activated only for specific companies. Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) 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 Dec 31, 2023 Planned removal of Sales Order API endpoints 05.05.2023 - Due date is now changed. We plan to be functional complete 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, 22.03.2023 - This is now in consideration. New dates for the deadline will come. 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 Dec 31, 2024   ... View more