Issue when Using SalesOrdersv3 to add orders with existing ordernumber

[erik-kle]

When adding SalesOrders in v3, the api demands Numbering set to UserNumbering and not only AllowOverrideUserNumbering. 

In the older versions (both v1 and v2) it is possible to use AllowOverridUserNumbering. 

This change is really bad if your customer uses the same numbering for both manually created orders inside Visma.Net and import using the api.

[Joni Wolff]

Hi! This has now been solved, "overrideNumberSeries" has been introduced in POST salesOrders

https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Sales-Order-Service-API-1-...

[erik-kle]

In this case we have added a new Ordertype so we can have two different numer series. 

One on imported orders where the webshop sets the number, and regular SO to use when doing manual orders inside Visma Net.
That is easy when having a new customer and a new system. 

At some point we all need to migrate from v1 and v2 to v3 on exsisting customer with existing logic. 
That is when there might be problem depending on how much logic is used. Changing the configuration inside Visma Net on processes, flow and integrations takes time.

[Marten Voort]

Do you want the salesorders to have consecutive numbering from one numbering range, or do you want two seperate number series? One automatic numbering series for salesorders manually entered and one directed by the api?