welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...

image
Blog

Exploring the Basics of Optimistic Concurrency Control

By Anurag on 9/28/2023

What is Optimistic concurrency control?

The optimistic concurrency feature allows your applications to check if a table record has been altered on the server during the period between when your application initially fetched the record and when it attempts to modify or remove that record.

How to enable optimistic concurrency?

To activate the optimistic concurrency checking functionality while performing an UpdateRequest, you can achieve this by configuring the ConcurrencyBehavior property of the request as IfRowVersionMatches. Likewise, when executing a DeleteRequest, you would also adjust the ConcurrencyBehavior property accordingly.

When working within the .NET SDK context to make alterations to data, make sure to specify the ConcurrencyBehavior on the OrganizationServiceContext object. This value will be passed through to all the UpdateRequest and DeleteRequest messages used by the OrganizationServiceContext when SaveChanges () is called.

You can exclusively configure the optimistic concurrency behavior through an SDK API call. Currently, there is no option to adjust it within the web application interface.

How to apply optimistic concurrency using SDK for .NET?

You can specify the optimistic concurrency behavior for an operation by configuring the ConcurrencyBehavior property within the UpdateRequest or DeleteRequest classes.

The process of updating or deleting a row may be based on potentially outdated data. If the current data differs because it has been modified since retrieval, optimistic concurrency provides a mechanism to abort an update or delete operation. This allows you to retrieve the most recent data and determine whether to proceed accordingly.

To ascertain whether the row has been altered, there's no need to compare all the values individually. You can simply utilize the RowVersion property to check for changes.

The following example succeeds only when:

1. The RowVersion of the row in the database is 986323.

2. The account table is enabled for optimistic concurrency (EntityMetadata.IsOptimisticConcurrencyEnabled property is true)

3. The RowVersion property is configured for the row included in the request.

If the RowVersion does not match, an error message will be generated, stating: 'The version of the existing record does not match the provided RowVersion property.

Preventing Simultaneous Modifications by Multiple Users on the same record-

The Dynamics CRM is used by multiple users. The likelihood of multiple users attempting to update the same record simultaneously is quite significant. In such a scenario, the modifications made by the most recent user will be preserved, leading to inconsistent data when users update the same fields simultaneously. Consequently, the Microsoft Xrm SDK offers a concurrency control mechanism when updating and deleting records using UpdateRequest and DeleteRequest, respectively.

Note: - To use the concurrency control mechanism of the Microsoft Xrm SDK, you must import the Microsoft.Xrm.Sdk namespace (i.e., using Microsoft.Xrm.Sdk;).

Here is a code implementation of a concurrency control mechanism:

In that case, if you call service.Execute(), it will result in an exception: "The version of the existing record doesn't match the provided RowVersion property," and the execution will not be successful.

If you wish to perform the Update operation through code without any concurrency checks, simply modify this line as follows:

Similarly, you can maintain concurrency control when deleting the record using DeleteRequest, as outlined below:

#ApplyingOptimisticConcurrency
#OptimisticConcurrencyBasics
#RowVersionProperty
Author
Blog Calendar
Blog Calendar List
2024 Apr  18  4
2024 Mar  37  4
2024 Feb  33  3
2024 Jan  9  7
2023 Dec  15  6
2023 Nov  73  5
2023 Oct  143  12
2023 Sep  306  9
2023 Aug  69  7
2023 Jul  32  5
2023 Jun  20  4
2023 May  43  5
2023 Apr  36  5
2023 Mar  102  6
2023 Feb  125  5
2023 Jan  43  4
2022 Dec  94  7
2022 Nov  259  2
2022 Sep  13  1
2022 Aug  28  2
2022 Jun  7  2
2022 May  4  2
2022 Apr  6  2
2022 Mar  2  1
2022 Feb  2  1
2022 Jan  1  1
2021 Dec  4  1
2021 Nov  2  1
2021 Oct  2  1
2021 Sep  12  1
2021 Aug  38  5
2021 Jul  36  4
2021 Jun  1292  5
2021 May  32  3
2021 Apr  2056  3
2021 Mar  190  5
2021 Feb  2189  7
2021 Jan  3172  9
2020 Dec  458  7
2020 Sep  75  3
2020 Aug  695  3
2020 Jul  130  1
2020 Jun  75  3
2020 Apr  69  3
2020 Mar  13  2
2020 Feb  28  5
2020 Jan  34  7
2019 Dec  17  4
2019 Nov  30  1
2019 Jan  23  2
2018 Dec  76  4
2018 Nov  68  3
2018 Oct  18  3
2018 Sep  1162  11
2018 Aug  7  2
2018 Jun  14  1
2018 Jan  68  2
2017 Sep  585  5
2017 Aug  17  1
2017 Jul  17  2
2017 Jun  62  2
2017 May  21  1
2017 Apr  37  2
2017 Mar  135  4
2017 Feb  792  4
2016 Dec  204  3
2016 Nov  843  8
2016 Oct  307  10
2016 Sep  713  6
2016 Aug  39  1
2016 Jun  1879  6
2016 May  110  3
2016 Jan  71  2
2015 Dec  496  6
2015 Nov  4  1
2015 Oct  13  1
2015 Sep  1468  6
2015 Aug  14  1
2015 Jul  128  2
2015 Jun  11  1
2015 May  20  1
2015 Apr  30  3
2015 Mar  80  3
2015 Jan  5335  4
2014 Dec  17  1
2014 Nov  2258  4
2014 Oct  68  1
2014 Sep  107  2
2014 Aug  5284  1
2014 Jul  49  2
2014 Apr  2579  12
2014 Mar  301  17
2014 Feb  220  6
2014 Jan  1510  16
2013 Dec  21  2
2013 Nov  690  2
2013 Oct  256  3
2013 Sep  11  1
2013 Aug  40  3
2013 Jul  214  1
2013 Apr  57  6
2013 Mar  2293  10
2013 Feb  127  3
2013 Jan  344  2
2012 Nov  57  2
2012 Oct  499  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote