Document (record) level locking to prevent multiple user access to the same record(s)

Hi,

Sorry but I don't know Mongoose. But this type of functionality always comes with a cost. I would suggest adding a date field and a user field so that there is some automatic recovery when x time has passed from when the lock was taken. Just so that the logic might clear that lock even though it's locked. I hope you get an answer to your question.

There should an InWorkflow property on every table, when you review the IDO properties you will see this is defined as a 'row lock' check the help for more information on how this works.

Set this tinyint to a non-zero value and the row is effectively locked for update in the UI.

As Karin mentions if you are going to allow people to lock then you also need an unlock mechanism. There is a very a good reason why multi-user systems use optimistic locking and a RecordDate or ChangeID to indicate if the record on screen is dirty when attempting to perform a save.

If you wish to bypass the standard behaviour do some testing to make sure you're getting the desired result.

BradleyBrown

Appreciate the responses.

I'm also aware of the reasons why record locking is a poor idea... hence some trepidation over implementing a straight record lock. I've got experience with record locks in other ERPs and they're always troublesome.

I knew of the Read Only Record flag on an IDO property but wasn't aware the InWorkflow property was one I could use, figuring it was for framework use. I'm not finding specific help on that property though, except for a blurb in the AES section on suspending events. (docs.infor.com)

I'd prefer to use whatever the framework is providing if at all possible.

I believe you can use it yourself, however if you are uncertain you can define your own lock property, and check the read-only record flag. when a read-only record property is set it makes the row read-only in the UI, which means scripts can lock/unlock rows.

docs.infor.com/.../default.html

If help is in any way lacking, there is a feedback form on the bottom of every page

BradleyBrown

Thanks again. I'll look into this further when I have more time later this week.

But, wouldn't setting this property while the user is working with the data lock it for that user as well, once the property was set/saved?