to get a personalized navigation.
to get a personalized navigation.
Release Notes |
Documentation |
Unable to release voided purchase credit note that was re-opened |
In the documents flow where a purchase credit note was; 1. Pre-booked 2. Voided 3. Re-opened into balanced state 4. Releasing the document gave an error "subaccount cannot be empty" This has now been fixed, and purchase credit notes that have been re-opened can be pre-booked and/or released via both UI and API. |
API - Due dates for breaking changes
Release Notes |
Documentation |
Due |
Deprecated parameters on GET Packagingtype endpoint |
In version 10.43.0 we have introduced pagination to enhance API performance and usability. As part of this update, the following parameters have been marked as deprecated: -GeaterThanValue -numberToRead -skipRecordsThis -orderBy These parameters will be removed in 6 months, at which point this update will result in a breaking change to the API. Please update your integrations accordingly to accommodate this change before the due date. |
|
Deprecated parameter releasedBatch on JournalTransactionV2 GET |
In version 10.39.0 we have introduced a new parameter, status, to filter on different statuses on journal transactions and marked releasedBatch as deprecated. We will remove releasedBatch parameter on May 13th 2025. |
May 13, 2025 |
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: 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 |
Copyright © 2022 Visma.com. All rights reserved.