[Release Notes] - Visma.Net API 9.08.0 - 02.08.2022

[#1]

Release Notes	Documentation
Inner exception and stack trace displayed when receiving error on GET Customer with attribute filter	Previously, when filtering on attributes on the GET Customer API endpoint, you could in some scenarios get an inner exception displayed in the response. This has now been fixed. In addition, the Swagger documentation for the GET Customer, GET Inventory and GET CustomerContract endpoints, related to filtering on attributes, has been improved.
POST V2/salesorder/{salesOrderNbr}/action/createShipment always results in a customer ledger document of the Credit note type	Earlier, for shipments created via the POST V2/salesorder/{salesOrderNbr}/action/createShipment endpoint, the Prepare invoice action always created invoices for the type Credit note. This has now been fixed.
Wrong "Location" URL returned after successful POST CustomerCreditNoteV2 request	Earlier, the wrong "Location" URL was returned after a successful POST CustomerCreditNoteV2 request. This has now been fixed.

Due dates for breaking changes

Release Notes	Documentation	Due
Breaking change on Branch endpoint	The following flags on the Branch endpoint will be set to false by default starting the 13. of September 2022:  - expandAddress  - expandContact  - expandCurrency  - expandVatZone  - expandLedger  - expandIndustryCode  - expandDeliveryAddress  - expandDeliveryContact  - expandDefaultCountry	Sep 13, 2022
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