Maximo Open Forum

HI All, I'm having an issue from a user when attempting to complete a task on a work order, we get the BMXAA8229W - Record WORKORDER updated by another user.

I have looked at the logs, but not much there or I haven't found the right place.  I have researched on line and some are pointing to a duplicate ID or rowstamp.  I was hoping someone would have a script they have used the will at least point me in the right direction.  One site said there is an automation script out there.  I'm hesitant to upload anything directly from an unknown site as this is a government system.  Any thoughts would be appreciated.  Thanks..

#Administration
#MaximoApplicationSuite

------------------------------
Brian Swanson
MSTS (Mission Support & Testing Services)
------------------------------

Many times this issue happens due to multiple scripts or (script+escalation) running at the same time on the same object and calling the same event. To identify exactly what triggers this, you may need to check either the UI session logs or the sysout log. at very high-level error that occurs while updating the rowstamp or timepstamp in Maximo, and the error comes under the MXRowUpdateException category.

------------------------------
Vivek Nagre
JLL
------------------------------

I wrote a script to identify these issues and a corresponding post which you can find here: https://www.sharptree.io/blog/2023/2023-07-25-updated-by-another-user/

If you have questions feel free to reach out.  

Jaso 

------------------------------
Jason VenHuizen
Sharptree
------------------------------

Hello Brian,

For us when I've noticed something like this it was due to 2 people having something open at the same time.  From what I understand 2 people cannot be working on the same thing at the same time.  One person will save, but the other will have to go out to the list view and come back in to be able to update and save.

------------------------------
Danny Richardson
Maximo Administrator Manager
Technimark LLC
------------------------------

If you have a Dev system that's same as Prod, then just as a starting point, I'd try using Admin Mode in the Dev instance and see if you encounter the same issue.  This way, all your Automation Scripts would not run.  That would at least quickly point out if a Script is contributing to the problem.

------------------------------
Travis Herron
Pensacola Christian College
------------------------------