SalesOrders v3 - Error 500 on customer, but not another

[Theis]

We switched from SalesOrders v2 to v3 for a client, using the service API token authorization.

The orders keep failing, we get this error "Error: 500 - "" at createError.

If we switch the same flow, same message and everything to our demo account, then order is posted fine.

If we switch back to v2 with same order details, it is posted fine to customers account.

Tested authentication and that is working fine, we can see the scope includes what is needed.

Tested in in Postman and our integration tool, both just gives the same error.

[Gabriella Hennings]

Do we have any news or updates concerning this problem? 

It's is still a problem for us, we can not create order on some customers, I get no error message. just 500 in response, and I can create the same order with the same details in the gui, and a can create the same order on a different customer without getting 500 error.

[Magnus Johnsen]

Hi,

The development team are solving these issues as they get information on them, if you could send us the json and compnay id we can forward it to the development team for investigation. 

[Theis]

The issue we were experiencing was solved by the development team, but not sure what the root cause was or what the fix was. So can´t say if it resolved anything for other people or if dev team prefers we send them these messages each time.

[Magnus Johnsen]

Hi,

Could you please send us the JSON sent and what company you are having the issue with?

We are currently working on a fix, any information provided will help.

Thank you. 

[Theis]

How do you prefer to receive the JSON message?

[Magnus Johnsen]

You can send it to developersupport@visma.com and we'll forward it to the development team. 

Thank you. 

[adrianm]

We all have different issues returning empty responses.

You need to go back to the drawing board and design something which doesn't return empty error messages so we have a chance of fixing (at least some) problems without collecting json etc and posting here.

[Gabriella Hennings]

+1 we also experience the same error

[adrianm]

The error handling in Sales Order V3 is far from production ready.

Returning 500 with empty message is standard except for a few cases.

It took years before the Visma.Net Api stopped responding "Another user has updated..." for generic errors. Please don't let us go through that again.

[erik-kle]

+ 1 
We experience the same error for POST Salesorder in v3