Errors after Visma update today - Critical

[Steinar Møller]

We getting errors on all posting from e-commerce after today Visma.net update.

1.
System.Exception: Fail: {"message":"Error: Inserting 'Sales order line' record raised at least one error. Please review the errors.\r\nError: 'Warehouse' cannot be empty.\r\n"}

2.
The order IO 2000021918 does not contain any items planned for shipment on 09/08/2022 00:00:00

No changes has been done on our side, and we now are being spammed with errors from all integration posting salesorders.

Please look into this asap, all our customers are affected, 

[Magnus Johnsen]

Hi,

Version 9.09.1 has now been released, which should solve the issues introduced to the salesOrder/V2 endpoint after the v. 9.09.0 release.

Please let us know if you are still having issues.  

[Steinar Møller]

Same issue with lineDescription on salesoderV2. The description is not being posted from the code. 

[Magnus Johnsen]

We'll forward this to the developers.

Thank you.

[erik-kle]

A customer reports that lineDescription and uom is not posted. So this bug is probably back. 

IPP-REQUEST-ID: 0fa328f1-6b77-4c9a-a0f4-f51c3a73b4af

[Steinar Møller]

Hi,

Hope this will be fixed asap, we are getting several complaints from our customers that have this issue. This is critical.

[Magnus Johnsen]

The feature causing the issue has been toggled of and the fields are now available on post. 

[Magnus Johnsen]

Hi,

We have confirmed that lineDescription and UoM is omitted when posting, we'll open a case with the developers.

For now the workaround is to send this in a PUT. 

[erik-kle]

A workaround in multiple live integrations, takes days to implement.

This is the 4th consecutive upgrade this summer that introduces breaking bugs. All seems to be releated. Do Visma have a plan for testing so this can be avoided in future updates?

[Magnus Johnsen]

We are waiting for more information from the developer team. Meanwhile, the feature causing the issue has been toggled of and the fields are now available on post. 

[erik-kle]

We can no longer set warehouse on lines, it defaults to the default for each product. This is validated on two separate customers, and is still an issue. 

Fix it now!!!!

[Magnus Johnsen]

Hi,

We'll inform the development team.

[erik-kle]

This started yesterday around 15 12 i think. 
All orders imported after that have ended up on wrong warehouses. 
So either I or the customers must now allocate time to fix this on every single order. 

This is the second time this summer that Visma upgrades introduces bugs that are tedious to fix. I cannot charge customers for this.

[Magnus Johnsen]

Is there any difference on orders created between 12:00 and 12:40 when the feature was deactivated?

[erik-kle]

No, the first order with the issue was created 2022-08-09 12:05:26 in the api, and after that all orders have this issue, even orders created now. 

[Magnus Johnsen]

Ok, thank you. We have informed the developers. 

[Magnus Johnsen]

Hi,

Could you please send us the JSON of one of these orders and we'll have a look.

Are both of these errors occurring when you post to salesOrder?

Thank you!

[Magnus Johnsen]

The feature that introduced the issue has been deactivated for now, the team is investigating the issue. 

https://status.visma.com/incidents/hlqxjphxjt4m

[Steinar Møller]

SalesOrderV2 endpoint