Skip to main content

Abort event through plugins

Suppose you are writing a pre -event plugin in which you compare to 
old and new values and on certain condition would like to cancel the Save or 
Update and stop the execution, it was simple in CRM 3 with an Abort() method
while in CRM 4, you have to manually raise and throw a 
Invalid-Plugin-Exception, while this gives a dirty error message on your MSCRM screen,
you can make it better by entering you own Message explaining why the record could
not be saved:

throw new InvalidPluginExecutionException("Execution has been stopped due to this reason");


OuSs said…
Thank you for this post,
I wonder if there are any way to do the same thing but without writing the entry caused by this in eventlog?

Thank you
Allo said…
What CRM does not seem to recognize is that sometimes there's the need for a Pre-stage plugin that would execute pretty much as an INSTEAD OF UPDATE/CREATE/DELETE trigger would in MS SQL. Say, a modification to a given field in certain conditions might have to be "cancelled" and instead treated as INSERT of another record/object. Why is there no simple way of setting something like Context.Abort = true ?
- Just treat the operation as if it had already completed successfully, and let the plug-in take care of the rest. Design flaws like this fly in the face of the claims that Dynamics CRM is a one-for-all business platform.
Can we do the same thing without throwing an exception in CRM 4.0?
i don't want the user to see an exception.i just want to stop the action done (delete, save...).
thank you.
hero said…
Hi Charles, thanks for the post, i will see if i can get an answer to this.
thank you for your prompt reply
Anything? I need this "instead-of" functionality in CRM 2011.

Popular posts from this blog

Microsoft reuse windows media player toolbar in Windows 7

Those who have been using Windows Media Player would have experienced one thing over time, when you click on the little up-down arrow heads on the right, you could see a thumbnail live view of the current movie you were playing. This had been since Window XP and now Microsoft have copy-pasted this code to show live preview of each taskbar window like a folder, browser session, office documents and every possible item you can open and appear in task bar.  Those of you who haven't seen Windows 7, this is how taskbar preview looks like :

Cancel Workflow job programmatically - CRM v.4

How many times you had to created a workflow on some date like Due date which keeps changing as per client's request. While this may sound simple in business, on CRM you have a workflow that may be waiting till this date and send a reminder exactly a week before. So you need to keep calling this workflow every time the date is updated, to make the matters more complicated, all the previous jobs that had initiated due to past modification will keep running and chasing that date which is never going to occur. What you do now, manually cancel those to save system resources and stop the never ending system jobs. There is a way to do it through SDK, in my case I call this function as a custom workflow activity in the first step of the workflow which Cancels any previous jobs of this workflow.   #region Cancel My WFs             QueryExpression qe = new QueryExpression();             qe.EntityName = EntityName.asyncoperation.ToString();             ColumnSet cs = new

Capture and Handle event when one entity record is attached through a Many to Many relationship - MS CRM 4

If you have already dug up too much about trying to capture the event when an entity record in MS CRM is attached ~ linked to a record in many to many relationship. For example, if you have two entities : Supplier and Company in MS CRM where a supplier can do business with many companies and at the same time a Company can order stuff from many suppliers. What if you want to send some notification whenever a new supplier or an existing supplier is linked to a company; similarly you may want to send a notification when a Supplier signs a deal with 2-3 companies and gets linked to those. Some experts from MS CRM fraternity have suggested some ways to over ride this limitation of MS CRM that it does not expose any event for the above mentioned scenario, below is one of the examples: But making changes to the default plugin model of MS CRM to add Associate or Disassociate event is not so eas