Preventing multiple users processing the same order?

(0) Share

Report

Posted on by Dan_AX

Hi all,

I have a customer requirement, which is that only one user is allowed in a specific sales order at any one time, to prevent issues when processing. This is due to them having numerous orders coming in at the same time, and do not want users adjusting price/confirming ect. when another user may be active in that order.

Just wondered if there is there any standard functionality in the system which could be used to block/prevent entry into a sales order if another user is in it?

Thanks,

Dan

*This post is locked for comments

All responses (3)

Answers (1)

Dan_AX 20 on at

Like (0)

Report

RE: Preventing multiple users processing the same order?

Hi Declan,

Thanks for your response.

We have tested it in a few different scenarios, and that error does appear if, for example, two users try to edit a sales order line, and enter different quantities. However, if for example 2 users are in an order at the same time, and both select to add a new sales order line (the same line for instance), when they both refresh both lines will have been added to the order, without error.

The error you mentioned would prevent a large proportion of the problems occurring though.

Dan
Suggested answer

feelyd 260 on at

Like (0)

Report

RE: Preventing multiple users processing the same order?

Have you tested the scenario your are referring to.

Normally what happens, when you open a sales order and make some changes, another person who has also opened the same sales order, will get an error if they try and save any details.

You normally get an error, "the current values are not up to date". This prevents two persons changing the same order at the same time.

The second person would have to refresh the form to get the most recent changes.

Declan
Verified answer

Sohaib Cheema 46,610 User Group Leader on at

Like (2)

Report

RE: Preventing multiple users processing the same order? AX R3

Not anything that I can think of, from Standard AX.

However you may replicate the Journals locking functionality, which locks a journal as soon as a user opens the lines. Meanwhile if a user tries to retrieve such lines, it is not allowed to do so. The lock is released as soon as release the journal. In the standard AX it keeps the lock information within the Journal Header table. To improve that you may want to maintain the information in a separate table for the sales orders, or else SalesTable.UpdatedDateTime may go wrong.