[Release Notes] - Visma.net API 10.37.0

[#1]

Release Notes	Documentation
Introduce new custom fields in purchaseOrder- endpoints	Introduce new custom fields for purchaseOrder- and purchaseOrderBasic -endpoints  (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  Valid for:  POST v1/purchaseOrder  PUT v1/purchaseOrder  GET v1/purchaseOrder?IncludeCustomFreeField  GET v1/purchaseOrder/[ordernumber]?IncludeCustomFreeField  POST v1/purchaseOrderBasic  PUT v1/purchaseOrderBasic  GET v1/purchaseOrderBasic?IncludeCustomFreeField  GET v1/purchaseOrderBasic/[ordernumber]?IncludeCustomFreeField
Introduce new custom fields in shipment- endpoints	Introduce new custom fields for shipment-endpoints (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  valid for:  GET v1/shipment[shipmentNbr]?IncludeCustomFreeFields=true  GET v1/shipment?IncludeCustomFreeFields  PUT v1/shipment[shipmentNbr]  POST v1/shipment
Introduce new custom fields in  purchaseReceipt-endpoints	Introduce new custom fields for purchasereceipt- and purchasereceiptBasic -endpoints  (header and lines):  - CustomStr1  - CustomStr2  - CustomStr3  - CustomStr4  - CustomStr5  - CustomDec1  - CustomDec2  - CustomInt1  - CustomInt2  - CustomDateTimeUtc1  Valid for:  POST v1/purchaseReceipt  PUT v1/purchaseReceipt  POST v1/purchaseOrderBasic  PUT v1/purchaseOrderBasic  GET v2/purchasereceipt?IncludeCustomFreeFields=true  GET v2/purchasereceipt/[receiptNbr]?IncludeCustomFreeFields=true  GET v1/PurchaseReceiptBasic?IncludeCustomFreeFields=true  GET v1/PurchaseReceiptBasic/[receiptNbr]?IncludeCustomFreeFields=true

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 the future.  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-s...  ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API  https://salesorder.visma.net/swagger/index.html	Sept   30,  2025