# "Row has been modified by another user and couldn't be updated" during site change for release

**URL:** <https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605>\
**Category:** Epicor ERP 10\
**Tags:** e10, epicor\
**Created:** [September 22, 2022, 2:29pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605 "2022-09-22T14:29:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tsantaniello](https://www.epiusers.help/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tsantaniello](https://www.epiusers.help/u/tsantaniello)\
**Post date:** [September 22, 2022, 2:29pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/1 "2022-09-22T14:29:37Z")

</div>

A PO arrived into demand entry (EDI) and was converted to a Sales Order. Every time we change the site for the release of the sales kit, we get the “Row has been modified by another user and couldn’t be updated” error message. We verified it happens in the base form as well. I have reviewed all the kits and their components to ensure that they exist in the desired warehouses and bins. Any assistance is greatly appreciated. Thanks.

Including the error message detail for those that can make sense of it:

_Business Layer Exception_

_Row has been modified by another user and couldn’t be updated._

_Exception caught in: Epicor.ServiceModel_

\*Error Detail \*  
_============_  
_Correlation ID: 8a88e0cf-7168-48bf-ae76-4c4a5b4874f0_  
_Description: Row has been modified by another user and couldn’t be updated._  
_Program: Epicor.Ice.dll_  
_Method: Validate_  
_Line Number: 109_  
_Column Number: 21_  
_Table: OrderRel_  
_Field: SysRevID_

\*Client Stack Trace \*  
_==================_

- at Epicor.ServiceModel.Channels.ImplBase`1.ShouldRethrowNonRetryableException(Exception ex, DataSet[] dataSets)\*
- at Erp.Proxy.BO.SalesOrderImpl.MasterUpdate(Boolean lCheckForOrderChangedMsg, Boolean lcheckForResponse, String cTableName, Int32 iCustNum, Int32 iOrderNum, Boolean lweLicensed, Boolean& lContinue, String& cResponseMsg, String& cCreditShipAction, String& cDisplayMsg, String& cCompliantMsg, String& cResponseMsgOrdRel, String& cAgingMessage, SalesOrderDataSet ds)\*
- at Erp.Adapters.SalesOrderAdapter.MasterUpdate(Boolean lCheckForOrderChangedMsg, Boolean lcheckForResponse, String cTableName, Int32 iCustNum, Int32 iOrderNum, Boolean lweLicensed, Boolean& lContinue, String& cResponseMsg, String& cCreditShipAction, String& cDisplayMsg, String& cCompliantMsg, String& cResponseMsgOrdRel, String& cAgingMessage)\*
- at Erp.UI.App.SalesOrderEntry.Transaction.Update()\*

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [September 22, 2022, 2:31pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/2 "2022-09-22T14:31:39Z")

</div>

Are there any Data Directive or Method Directives relating to Order tables impacting the OrderRel table?

---

<div class="post-metadata">

**Author:** ![tsantaniello](https://www.epiusers.help/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tsantaniello](https://www.epiusers.help/u/tsantaniello)\
**Post date:** [September 22, 2022, 2:37pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/3 "2022-09-22T14:37:29Z")

</div>

Yes, but BPMs were disabled by our consultants who were evaluating this issue. The error still occurred.

---

<div class="post-metadata">

**Author:** ![jgiese.wci](https://www.epiusers.help/user_avatar/www.epiusers.help/jgiese.wci/32/51553_2.png) [@jgiese.wci](https://www.epiusers.help/u/jgiese.wci)\
**Post date:** [September 22, 2022, 3:07pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/4 "2022-09-22T15:07:42Z")

</div>

If no BPMs and no Customizations it’s a bug

---

<div class="post-metadata">

**Author:** ![tsantaniello](https://www.epiusers.help/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tsantaniello](https://www.epiusers.help/u/tsantaniello)\
**Post date:** [September 22, 2022, 3:54pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/5 "2022-09-22T15:54:18Z")

</div>

I would agree on the bug conclusion, but I have resolved one of the lines. I tried the same procedure on the next line, but the error is still occurring for that line. Thus, it is definitely a data issue buried somewhere in the tables. What if I updated OrderRel.warehousecode and OrderRel.plant using DMT? Does the DemandDetail.Plant field value affect the Order Release site value?

---

<div class="post-metadata">

**Author:** ![tsantaniello](https://www.epiusers.help/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@tsantaniello](https://www.epiusers.help/u/tsantaniello)\
**Post date:** [September 22, 2022, 4:11pm UTC](https://www.epiusers.help/t/row-has-been-modified-by-another-user-and-couldnt-be-updated-during-site-change-for-release/94605/6 "2022-09-22T16:11:53Z")

</div>

Resolved…I tried my suggestion and it worked.
