2024.1 - Nearly CONSTANT: Row has been modified by another user and couldn't be updated

[Adam (Adam Szymanski)]

Make it stop!?!? We are relatively new to Kinetic 2024.1.10 browser based On Prem and users complain that this popup comes up all day, on SO many screens. An engineer just showed me his engineering workbench group screen where you simply pick a group ID and it popped up. He said when he’s creating a new part that no one knows it pops up. Accounting, Shipping, Customer Server, etc. Everyone gets this SO often.

They make a bunch of changes on their screen, hit save, and this error. Many are now hitting refresh on EVERY screen before they do anything, hoping that the submission will work, yet sometimes that doesn’t even prevent it.

Has anyone faced this wide range annoyance?

[utaylor (Utah Taylor)]

Do you have any BPMs or Data directives?

[Adam (Adam Szymanski)]

Yes to both.

[utaylor (Utah Taylor)]

I’m going to recommend something that I always hate because sometimes it’s not practical, but then again neither are these pop ups you’re getting, you should turn all those off and then see if the problem goes away.

@Hally may have some more refined advice for you. I hope!

[josecgomez]

@Adam

Yes to both.

99.99% of the time the issues arise because the BPM / DD is modifying the data set on the back end and the front end doesn’t know.

[dcamlin (David Camlin)]

@timshuwy had a nice explanation of this yesterday… doesn’t help solve your problem, but it helps explain the error:

@timshuwy

The error you are getting is because you are reading and then modifying the record after it was already written. Then in your screen, you don’t have the latest copy, so you get the “modified by another user”. the system doesn’t know who modified it… just that it has been modified. How does it know this? Well, there is a field called RowRev, which is an integer number… it is increased each time a change is made. when you attempt to change the record again, we look and if the value is higher in the database than the value you originally read, we know that something else changed it.

Keep in mind the “another user” could be yourself. Not necessarily someone else.

[Hally (Simon Hall)]

I agree with @utaylor.

Being on prem you can turn them all off in bulk by updating the hosts.config. Customizations key if I recall.

That will be a quick check. But don’t do it in Production, you are diagnosing the problem. I am making the assumption you can replicate the issues in a test environment.

Next would be to work through each bpm and review.

I am guessing you are updating the data tables behind the scenes and that’s why you are getting the errors.

If it is happening all over the place then I’d be trying to see if there is any commonly executed bpms or scheduled functions that are running any database updates.

There a quite a few posts her on this particular problem

Sounds like a good post for guide on how to identify and possible rectification paths.

[Hally (Simon Hall)]

@dcamlin

another user

Good point

[utaylor (Utah Taylor)]

@Hally

Being on prem you can turn them all off in bulk by updating the hosts.config. Customizations key if I recall.

I believe this still works in Kinetic, haven’t tried.

[utaylor (Utah Taylor)]

I thought also you could do some kind of trace, for example, a trace on that engineering workbench and see all the calls that happened, both client and server… is that accurate? Then you could see exactly what BPMs fired, etC?

It’d only be specific to the one instance that OP is trying to work on, but…

I think you can do a client trace and get this detail, but not sure. Maybe would have to reference server log and turn on relevant logging options at server level… not exactly sure.

[Hally (Simon Hall)]

Oh just out of interest users aren’t opening The same screen more than once or having multiple browsers open at once?

FYI In classic you have the ability hold down ctrl+shift and then open an already open screen so you had two instances open at the same time.

[Adam (Adam Szymanski)]

Sometimes they open the same screen, but then pull in a different record, e.g. a different customer.

[Adam (Adam Szymanski)]

Thanks for all of the feedback! I wish I could find a path to duplicate this in TEST so that I could work through the DD/BPMs. Currently no user has been able to show me a repeatable pattern.

[utaylor (Utah Taylor)]

Does TEST have the same BPMs and Data directives in it??

[Adam (Adam Szymanski)]

Yes, but I can’t get the error in TEST.

[Hally (Simon Hall)]

Ouch

[utaylor (Utah Taylor)]

Like Jose said, it’s some BPM or DD updating something on the back end and the front end doesn’t know.

Most likely there is someone else in the system that’s firing a BPM that affects your user at the time they are doing their thing.

Do you have the same form customizations in your test environment as well?

[Hally (Simon Hall)]

Might be a long shot but try confirming you database options

[Adam (Adam Szymanski)]

@utaylor - Yes, TEST is a mirror of LIVE.

@Hally - “confirming your database options”? What do you mean?

[Hally (Simon Hall)]

Easiest is to run the PDT tool abs check your server configuration for both live and test. Take a look at the sql section of the results. Adjust the database options as required. Forced paramaterization and prallellisim seffuon to 2 (I think… not in front of a computer)