[Release Notes] - Visma.Net API 9.19.0 - 25.10.2022

[#1]

Release Notes	Documentation
Field Bank Detail Type exposed in PaymentMethod endpoint	Previously, the Bank Detail Type field was not returned by the PaymentMethod endpoint. This has now been fixed.
SupplierPayment endpoint returns wrong data when payments and credit notes have the same reference number	Previously, both GET ALL and GET Specific - SupplierPayment endpoints returned the wrong data when payments and credit notes had the same reference number. This has now been fixed, but please note the following: 1.Get ALL SupplierPayment endpoint will return the correct header details and invoice lines applied against each payment document 2. The initial Get SPECIFIC SupplierPayment endpoint (controller/api/v1/SupplierPayment /paymentnumber), in order to be backward compatible, will return only one document, being the payment OR the credit note depending on the used filters. 3. A NEW endpoint Get SPECIFIC SupplierPayment endpoint has been deployed by type and number (controller/api/v1/SupplierPayment /paymenttype/paymentnumber). This one will return the correct information depending on the chosen document.
Unable to update a purchase receipt's supplier ID via API	Earlier, it was not possible to update "supplierId" in the PUT PurchaseReceipt endpoint. This has now been fixed.
SupplierInvoice endpoint not allowing negative retainage	Previously, when creating an invoice via API, you were not allowed to enter a negative retainage amount. This has now been fixed.

 Due dates for breaking change

Release Notes	Documentation	Due
Planned removal of Sales Order API endpoints	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-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html	Jun 01, 2023