LogisticsElectronicAddress - update conflict exception for non-phone numbers

(0) Share

Report

Posted on by Community member

Hello:

I am attempting to update an email record in LogisticsElectronicAddress table from the CustTable form and received the following error message:

/Cannot edit a record in Communication details (LogisticsElectronicAddress). An update conflict occurred due to another user process deleting the record or changing one or more fields in the record./

I do not receive such an error when I try to update a record with method type Phone - my change is accepted. I have attempted to call reread() and disableCache() before modifying the record and calling the LogisticsElectronicAddress.update() method - still the same error. I have also attempted using the select forUpdate clause in place of the update() call and included the RecVersion in my select statement - still the same error.

Is there any way to tell where this other 'user process' is originating? I do not have any batch jobs running on separate server.

Thank you in advance.

I have the same question (0)

All responses (3)

Answers (1)

GirishS 27,825 Moderator on at

Like (0)

Report

LogisticsElectronicAddress - update conflict exception for non-phone numbers

Hi,

Have you debugged the code?

May be the update is calling 2 times - One will be from your custom update and another one from standard update.

Please debug to get better understanding about the issue.

If possible, please post the update code here.

Thanks,

Girish S.

Was this reply helpful? Yes No
Community member 11 on at

Like (0)

Report

LogisticsElectronicAddress - update conflict exception for non-phone numbers

Hello:

I ran through code with the debugger - there is only one update method call. It always errors when super() is called in LogisticsElectronicAddress.update(), so I am unable to see what operation is causing the issue. It also errors when I use doUpdate().

I have also tried to update values directly by opening the table in the AOT. Again, it works for Type = Phone, but nothing else.

I still do not understand why update conflict happens for some records but not others - shouldn't an update conflict occur on any update to the table?

Thank you again.

Was this reply helpful? Yes No
Verified answer

Community member 11 on at

Like (0)

Report

LogisticsElectronicAddress - update conflict exception for non-phone numbers

I was actually able to resolve it on my own. I had to disable optimistic currency control (OCC) at the table level AND include the table buffer in the same tts level as the update call.

1 people found this reply helpful.

Was this reply helpful? Yes No

Join the conversation

Community site session details

LogisticsElectronicAddress - update conflict exception for non-phone numbers

Helpful resources

Quick Links

Responsible AI policies

Pallavi Phade – Community Spotlight

Congratulations to the October Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

LogisticsElectronicAddress - update conflict exception for non-phone numbers

Helpful resources

Quick Links

Responsible AI policies

Pallavi Phade – Community Spotlight

Congratulations to the October Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates