Urgent - Placing orders suddenly receiving Error: 'Subaccount' cannot be empty

[Kjetil Ringstad]

Hi

Have there been any updates the past 24 hrs?

Several of our customers are now receiving errors stating subaccount cannot be empty on line level

"message": "Error: Inserting  'Sales order line' record raised at least one error. Please review the errors.\r\nError: 'Subaccount' cannot be empty.\r\n"

These are on integrations that's been working well for over a year. But this started last night from 21:30.

Which subaccount are you referring to?

Please advise, there are many orders now suddenly failing , and this has an impact on our customer's economy.

An example request is attached. 

At least companies 2516370 and 2505895 are affected.

[Magnus Johnsen]

The issue should now have been resolved, we would appreciate if you could confirm you are not having this issue any longer.

Thank you for your patience. 

[Kjetil Ringstad · Accepted solution]

It looks like the orders are being imported now, thank you .

[Magnus Johnsen]

Thank you for confirming it works, please let us know if you have any other issues.

[Magnus Johnsen]

@Anonymous Could you please confirm what country templates are used for your companies?

Thank you. 

[Kjetil Ringstad]

Both of the companies with the most errors, 2516370 and 2505895, are Swedish, but we were not involved in their initital configuration.

[Magnus Johnsen]

Thank you, the development team has confirmed that this only seems to affect SE companies. They are currently testing the solution.
We'll inform you when they have made more progress.

[andreasaulin]

Well, we do see this error for Norwegian companies.

[Magnus Johnsen]

Hi,

There is a known issue caused during the release yesterday evening, the community post can be found here:
https://community.visma.com/t5/Nyheter-i-Visma-net-ERP/Kjent-feil-Kostnadsbaerer-mangler-pa-salgsord...

This has been reported to the development team. 

[Kjetil Ringstad]

This results in API orders stopping. What do Visma want us to tell our customers? Should we stand by and resend when you have fixed it? Will it be fixed today?

[Magnus Johnsen]

This is currently being fixed, the case has a critical priority. As soon as we have more information to share we'll let you know. 

[Kjetil Ringstad]

It's now been one hour and orders are really starting to pile up. Status update, please?

[Magnus Johnsen]

There is an incident status here: https://status.visma.com/incidents/tbl1dxtsd1kn

The case is currently under development. 

[erik-kle]

Why is the release not visible in the incident history on https://status.visma.com/?

[Magnus Johnsen]

Hi,

As this was a "zero-downtime" update, no incident was posted, this was the same for version 8.30. 

[erik-kle]

Well, thats Vismas definition, i think all affected customers would not agree of it beeing a "zero-downtime" update. I think it would be good if you still post incidents of all updates, in order for us partners to faster pinpoint if a bug relates to a recent update

[Kjetil Ringstad]

Can you please add a note regarding releases anyway? This  saves us for a lot of time searching for errors locally.

[Magnus Johnsen]

On the forum we always post the notes under the News section: Visma.net Financials API updates for version 8.31.0 (December 2020)
Do you mean on the status page? We could raise this internally, we understand that this would make it a lot easier for you, especially since you would be able to catch it via the webhook notifications. 

[erik-kle]

Same problem here for multiple customers. This is really URGENT, christmas is in two days.