Release Notes
Documentation
Add allocations to kit assemblies to support industries using expiry dates or lot numbers
In API, you have the possibility to set the kit allocations for a Kit Assembly (POST / PUT), and you can now use stock items for the assembly to set the allocations for the stock items individually. This is important, for example, for food production where the different ingredients (stock components) used for producing an assembly need to have full control of the allocations, meaning the expiry date. To achieve this, the allocations for each stock component line are now exposed in the API (PUT/POST).
Release of purchase invoice via API missing link to batch, invoice stuck in Balanced status
This specific problem occurred in some occasions during heavy API load together with parallel actions, where the released purchase invoice may have incorrectly remained in the Balanced status after it was released via SupplierInvoice endpoint. In this scenario, the full release operation was not able to finish. Meaning even though the release process was successful, and a batch was created, if the batch failed to link the documents (the Financial details tab not showing a link to the batch no.), due to this the purchase invoice document remained in the Balanced status. This has now been fixed.
Due dates for breaking changes
Release Notes
Documentation
Due
Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch
At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. This change will be enforced starting the 20th of June 2023. The ones willing to switch to this new approach earlier can contact the partners, support, or development team.
Jun 20, 2023
Planned removal of Sales Order API endpoints
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
Jun 01, 2023
... View more
.gif "VISMA"){kind=icon}
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America