5

I wanted to confirm my understanding on managing transactions in Dynamics CRM and check if I am missing something.

1) Transactions in CRM Plugins: The plugins registered in the Stage 20 and 40 of the Event Pipeline run under DB transaction. So if I have three plugins registered on pre/post operation of any message and if the third plugin throws an exception, the changes done by the first two plugins would also be rolled back. Is this understanding correct?

2) Transactions in CRM Web Service: In case of writing code with CRM Web Services, I can make use ExecuteTransactionRequest request and all the request messages provided with this message would run under one CRM DB transaction. This message seems to be introduced in 2016 version so what would be the ideal way to handle such scenarios prior to 2016?

Ashish
  • 373
  • 1
  • 5
  • 15
  • Only changes made to the CRM database will be rolled back by the plugins. If your plugin updates another database (e.g. sync operations) then changes to that other database won't be rolled back – jasonscript Sep 20 '16 at 00:54
  • Here's the reference to the plugin stage numbers: https://learn.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg327941(v=crm.8)#pipeline-stages – Dave Potts Jan 17 '19 at 08:26

1 Answers1

5

1) Assuming the plugins all run synchronously, then yes, all changes should be rolled back.

Inclusion in database transactions

Plug-ins may or may not execute within the database transaction of the Microsoft Dynamics CRM platform. Whether a plug-in is part of the transaction is dependent on how the message request is processed by the pipeline. You can check if the plug-in is executing in-transaction by reading the IsInTransaction property inherited by IPluginExecutionContext that is passed to the plug-in. If a plug-in is executing in the database transaction and allows an exception to be passed back to the platform, the entire transaction will be rolled back. Stages 20 and 40 are guaranteed to be part of the database transaction while stage 10 may be part of the transaction.

Any registered plug-in that executes during the database transaction and that passes an exception back to the platform cancels the core operation. This results in a rollback of the core operation. In addition, any pre-event or post event registered plug-ins that have not yet executed and any workflow that is triggered by the same event that the plug-in was registered for will not execute.

2)

  • Yes ExecuteTransactionRequest is a new CRM 2016 feature.
  • If you have CRM 2013+ you could put the logic inside an Action which supports automatic rollback. Then call the action with inputs.
  • For CRM 2011, put the logic inside a plugin. Then cause the plugin to be triggered, for example by creating a record in CRM. You can also capture inputs on the new record.
James Wood
  • 17,286
  • 4
  • 46
  • 89
  • Thanks James. Just some follow-up questions. 1) So practically, is maintaining transactions not possible in aync plugins? And is this applicable only for multiple plugins registered on a message or applies even within a single plugin? – Ashish Sep 15 '16 at 03:29
  • The async plugin itself can be transactional, but it won't roll back to a previous sync plugin, as it will execute outside the transaction of the sync plugin. – James Wood Sep 15 '16 at 07:43