24 Jun, 2021
Posted on 24 Jun, 2021 by Admin, Posted in Dynamics 365
Blogs
As we know, Dynamics CRM is used by multiple users. So the possibility of modifying the same record at a time is very high. This can result into inconsistent data.
We can avoid this with the help of concurrency control mechanism using RowVersion property.
Below is a code implementing concurrency control mechanism:-
Now, if the name of the record is changed in CRM at the same time by a different user, before UpdateRequest is executed. Then, service.Execute() will give an Exception: “The version of the existing record doesn’t match the RowVersion property provided.” and it would not be executed successfully.
If you want to forcibly perform the Update operation through code, then, simply change this line as mentioned below:
updateReq.ConcurrencyBehavior = ConcurrencyBehavior.AlwaysOverwrite;
In the same way, concurrency control can be maintained, while deleting the record using DeleteRequest as mentioned below:
Comment
Most Power BI reports in a Dynamics 365 environment live somewhere the user has to go and find: a dashboard,…
READ MORE
Introduction Many times, we come across scenarios where we need to populate a Word template in Dynamics 365 using Power…
READ MORE
Overview Email Templates in Microsoft Dataverse make it easy to reuse email content such as subject lines, message bodies, and…
READ MORE