Migration guide to SalesOrder service?

[JohanFriedrichsen]

Do you have a list of parameters that have changed name so that it is possible to verify that we have 100% feature coverage?

Example from Finance-API (GET /controller/api/v1/salesorder/{orderType}/{orderNbr}):

"printDescriptionOnInvoice": true,
"printNoteOnExternalDocuments": true,
"printNoteOnInternalDocuments": true

Service:
"print": {
"descriptionOnInvoice": true,
"noteOnInternalDocuments": true,
"noteOnExternalDocuments": true
}

Service respons has different structure and parameter names which makes it very easy to miss missing features.

[JohanFriedrichsen]

Ok, but the Sales Order Service API should today contain features that cover the endpoints that are going to be removed in June?

[Yıldırım]

Hello, 

All functionality currently missing in the new Sales Order Service API has been planned to be added before removing the old endpoints. 

[Yıldırım]

Hello, 

currently, the new Sales Order Service API is not including all the features exposed via the legacy Sales Order Endpoint. We don't have a field to field map between old and new DTOs however the field definitions of the new service can be seen at https://salesorder.visma.net/swagger/index.html

 Getting started with the first neXtGen service: Visma.net ERP Sales Order API

Please let us know what information you're missing in detail, so we can check it out for you. 

Thanks.