Sales Order Entry screen Index -1 is either negative or above rows count. error for one user

Epicor ERP 10
1

Version 10.0.7.4

One user start getting this error Index -1 is either negative or above rows count.

It is not PC specific. It happens to that particular user account only.

I deleted all the personalisation still didn’t work, this is why I post the error here to see if anyone has a similar issue. Customisation turned off still the same…

Application Error

Exception caught in: System.Data

Error Detail

Message: Index -1 is either negative or above rows count.
Program: System.Data.dll
Method: GetRow

Client Stack Trace

at System.Data.DataView.GetRow(Int32 index)
at Erp.UI.App.SalesOrderEntry.Transaction.orderRelView_EpiViewNotification(EpiDataView view, EpiNotifyArgs args)
at Ice.Lib.Framework.EpiViewNotification.Invoke(EpiDataView view, EpiNotifyArgs args)
at Ice.Lib.Framework.EpiDataView.OnEpiViewNotification(EpiNotifyArgs e)
at Ice.Lib.Framework.EpiDataView.Notify(EpiNotifyArgs args)
at Ice.Lib.Framework.EpiTransaction.NotifyAllOthers(EpiDataView sourceView, Boolean changeGridPropsCurrentRowOnly, Boolean notifyTree, Guid notifyId)
at Ice.Lib.Framework.EpiDataView.Notify(EpiNotifyArgs args)
at Ice.Lib.Framework.EpiDataView.SetChildFilterAndNotifyChildViewWhenHasCurrentRow(EpiDataView childView, EpiNotifyArgs args, Boolean forceIt)
at Ice.Lib.Framework.EpiDataView.SetChildFiltersAndNotifyChildViews(EpiNotifyArgs args, Boolean forceIt)
at Ice.Lib.Framework.EpiDataView.Notify(EpiNotifyArgs args)
at Ice.Lib.Framework.EpiDataView.SetChildFilterAndNotifyChildViewWhenHasCurrentRow(EpiDataView childView, EpiNotifyArgs args, Boolean forceIt)
at Ice.Lib.Framework.EpiDataView.SetChildFiltersAndNotifyChildViews(EpiNotifyArgs args, Boolean forceIt)
at Ice.Lib.Framework.EpiDataView.Notify(EpiNotifyArgs args)
at Erp.UI.App.SalesOrderEntry.Transaction.GetOrderData(Int32 orderNum)

2

Try deleting the user’s personalization.

3

@Jason_Woods
why you are giving this suggestion. can you please explain it. for me also getting the same error in Lot Entry form accessed from Receipt Entry form.

4

A personalization is a layer built on top of the screen or customization. If either of the lower layers change, the personalization can cause errors.

5

I used customization only, but i’m getting the same error in LotEntryform.Launchform

I handled the null values also.

6

I’ve recently encountered the same issue. It was caused by a customization (not personalization). Best way to test this is to add a new Order Entry link that points to Order Entry without any customizations selected. Then have the user log in and try it. It worked for the case I had. The only two options at that point was to either try to fix or remove the customization or create a new user name for that user. (Also, make sure the user clears cache before testing).

I realize that there is a deeper issue here, which could possibly be due to a unique security setup for the user or the customization does something with the User table.