options for concurrency control in crm?

(0) Share

Report

Posted on by Community Member

Hello, does CRM have any options for concurrency control? For example, optimistic concurrency -vs- pessimistic concurrency? What about controlling concurrent updates at the field level -vs- at the row level?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Roshan G Palankar on at

Like (0)

Report

No There is no option like the one in AX in CRM.

Was this reply helpful? Yes No
Suggested answer

Aileen Gusni 44,524 on at

Like (0)

Report

Hi Andrew,

The CRM standard does not have that function. You may custom this, but it requires a lot of customization. Thanks.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ok - thanks for the feedback. So what would be the end result of the following use case?:

1. User1 and User2 both open the same existing case which has a Title value of "MyTitle" and no value for MyCustomField1.

2. User1 enters an updated value of "MyTitle1" in the Title field

3. User2 enters a value of "Test" in the MyCustomField1 field

4. Both users click the Save button at the exact same millisecond and both user requests hit the server at the exact same millisecond

What would be the end result of this scenario? Would CRM display an error dialog saying that the update could not be performed because of a conflict or would CRM randomly pick 1 of the requests as the winner? Based on your feedback it sounds like field-level concurrency could be eliminated as an expected end result.

Was this reply helpful? Yes No
Verified answer

ScottDurow 21 on at

Like (0)

Report

Hi Andrew,

CRM saves at the field level and so the last user to save wins - one of the transactions will 'win', There are no concurrency lock checks (optimistic or pessimistic) other than the database transaction level update locking.

In your scenario you will find that the record has the values from both users since only the values that are updated are saved by the form.

You can implement a optimistic locking mechanism by reading the last modified date when the record is opened, and then submit this in the transaction. The Plugin would then check the last modified date and ensure that it is the same. See blog.salesmetrix.com/.../concurrency-control-in-crm-2011

Hope this helps,

Scott

Was this reply helpful? Yes No