Recalling a suspend transaction in POS Error: 1002

(0) Share

Report

Posted on by Shafraz Khalik

159

when we suspend a transaction and try to recall, we are getting the Error: 1002.

in the event viewer we found below details,

LSRetailPosis.POSProcesses.frmSuspendedTrans, Text: : System.InvalidOperationException: Sequence contains more than one matching element
   at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at LSRetailPosis.BusinessLogic.BusinessLogicExtensions.PopulateDimensions(RetailTransaction retailTransaction)
   at LSRetailPosis.POSProcesses.frmSuspendedTrans.LoadTransaction(String transactionId)
   at LSRetailPosis.POSProcesses.frmSuspendedTrans.gridView1_FocusedRowChanged(Object sender, FocusedRowChangedEventArgs e).

Looking forward to suggestions to fix this...

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Rodolfo Recalde on at

Like (1)

Report

I Shafraz,

This transaction has been customized?

In this type of error , you might try to find out:

A. Debugging the POS.

B. Using SQL Server Profiler.

Probably, Some query is returning two or more records that are not supported by some process element. In SQL Server Profiler, Check the last query performed by the user before the error occurred. You can identify which record is duplicate.

I Hope this Helps!

Regards,

Rodolfo Recalde.

Was this reply helpful? Yes No
Shafraz Khalik 159 on at

Like (0)

Report

Hi Rodolfo,

Thank you for your reply, it is not customized but a normal transaction.

we found strange is it happened to few transactions..

As per your suggestion we used SQL profiler, and noticed that while recalling these transaction there are 2 lines with the same item-variants, where as the original suspended transaction has only one Item-variant.

will this be bug in CU12?

Regards,

Shafraz

Was this reply helpful? Yes No
Solozmar 796 on at

Like (0)

Report

I tried this out on our CU12 Retail environment (albeit, with our dataset) and can't reproduce this. I do see quite a few hotfixes around retail and recalls but could not find one that matches exactly to your issue.

Was this reply helpful? Yes No
Rodolfo Recalde on at

Like (0)

Report

I Shafraz,

I imagine this problem is occurring for some products in specific, correct? If yes, and if you can isolate these products. Check Product VariandID, Check if there is no inconsistency of data (or some customization that was done in AX that was not transapassed into the POS).

I do not have the CU12 scenario to test. You can opened a incident at Microsoft.

I Hope this Helps!

Regards,
Rodolfo Recalde.

Was this reply helpful? Yes No
Shafraz Khalik 159 on at

Like (1)

Report

Hi Rodolfo,

Yes you are correct, it happens to few variants. we had done extensive checking from our end and we were unable to find a pattern on this issue.

As you mentioned we opened an incident and waiting for the reply from Microsoft.

Regards,

Shafraz

Was this reply helpful? Yes No
Johnny J. on at

Like (1)

Report

We get the error for products having more than one barcode. But we have yet to find a workaround for it! :-(

Was this reply helpful? Yes No
Shafraz Khalik 159 on at

Like (2)

Report

Hi All,

Thank you for your valuable inputs.

we log a case with Microsoft and finally they agreed to come up with a Hotfix, and we are waiting for that release.

Cheers,

Shafraz

Was this reply helpful? Yes No