- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
[Release Notes] - Visma.Net API 10.38.0
Release Notes |
Documentation |
Align behaviour of v1 and v2 createShipment endpoint with UI |
Improved quality in v1 and v2 salesorder/[ordernumber]/action/createShipment endpoints regarding salesorderstatus |
Implementation of ETag/If-Match function ality in the supplier endpoints |
In supplier endpoints the ETag/If-Match functionality is now implemented. ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are trying to update the same resource at the same time and avoid data inconsistency. The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts when multiple clients are trying to update the same resource at the same time |
Implementation of ETag/If-Match function ality in the shipment endpoints |
In shipment endpoints the ETag/If-Match functionality is now implemented. ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are trying to update the same resource at the same time and avoid data inconsistency. The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts when multiple clients are trying to update the same resource at the same time |
Implementation of ETag/ifMatch functionality in the purchaseReceipt endpoint |
In purchaseReceipt endpoints the ETag/If-Match functionality is now implemented. ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are trying to update the same resource at the same time and avoid data inconsistency. The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts when multiple clients are trying to update the same resource at the same time |
Implementation of ETag/If-Match function ality in the purchaseOrder endpoints |
In purchaseOrder endpoints the ETag/If-Match functionality is now implemented. ETag and If-Match are HTTP headers that are used to prevent conflicts when multiple clients are trying to update the same resource at the same time and avoid data inconsistency. The main benefit is conflict prevention; by using If-Match headers, clients can prevent conflicts when multiple clients are trying to update the same resource at the same time |
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 at a later point. 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: ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html |