Skip to main content
Question

Multiple Business Events Updating Sales Orders Causing Concurrent Update Errors

  • June 30, 2026
  • 2 replies
  • 30 views

Forum|alt.badge.img

Hi Everyone,

We have multiple Business Events, each connected to its own Import Scenario, and all of them target the Sales Orders (SO301000) screen. Each Import Scenario updates different fields (Ship Via, Carrier/Class, Order Type, Prop 65 item, etc.), but they all save the same Sales Order.

When a Shopify order is imported, multiple Business Events are triggered at the same time, resulting in errors such as:

  • Another process has updated the 'SOOrder' record.
  • The system failed to commit the Document row.
  • Completed with Errors
  • 0 records of 1 processed / Subscriber not processed

Some Import Scenarios have Source Restrictions, while others don't, so merging them into a single Import Scenario isn't straightforward.

My questions are:

  1. What is the recommended Acumatica approach to avoid these concurrent update conflicts?
  2. Is it possible or recommended to have one Business Event with multiple Import Scenario subscribers instead of multiple Business Events?

2 replies

DrewNisley
Pro I
Forum|alt.badge.img+4
  • Pro I
  • June 30, 2026

If you are able to, put them under one business event. They will fire in order of how they are placed on the business event. I frequently put multiple subscribers under one business event.

Just make sure the Break on Error checkbox is unchecked unless you want the consecutive import scenarios to not fire if a previous one fails.

Hope this helps!


Forum|alt.badge.img+2

Further to ​@DrewNisley’s suggestion, if putting the two Import Scenarios under the same Business Event is not feasible, you could try chaining them to ensure they fire one after the other.

For example, update the trigger conditions of the second BE so that it only fires once the changes made by the first BE are detected.