The Battle Of Evermore…
OK, I admit it. I’ve caught the CRM development bug. What started as a harmless bit of fun working on document library integration between CRM & SharePoint has now developed into an obsession. In this post I will describe how to build a plug-in that examines the body of any e-mail promoted promoted from Outlook or the e-mail router and converts the HTML into plain text.
After a bit of searching, I found a good article which showed how you could use regular expressions to remove unwanted HTML tags leaving just the plain text – Convert HTML to Plain Text. Converting this from C# to VB (my preferred choice of language) and stripping out some of the bits I didn’t need, I came up with the following code which forms the basis of this plug-in.
All that remains is to implement the IPlugin.Execute method. In order to be able to modify the e-mail message before the e-mail activity gets created in the database, I had to figure out which event(s) to intercept. Through a bit of trial and error, I observed that any e-mail promoted from Outlook triggers the “DeliverPromote” event, whereas any incoming e-mail handled by the e-mail router triggers the “DeliverIncoming” event. Interestingly enough, the “Create” event was also called as a child pipeline for these events, but modifying the message here didn’t have any effect, even in the pre-processing stage.
Because plug-ins have the potential to introduce significant performance and scalability issues into your environment, it is important to ensure that the code is as efficient as possible. To that end I added additional checks to ensure that the even if registered on multiple events, the main code will only run if the plug-in:
- is running on the ‘DeliverPromote’ or ‘DeliverIncoming’ messages
- is running synchronously
- is running against the ‘Email’ entity
- is running in the ‘pre-processing’ stage of the pipeline
- is running in a ‘Parent’ pipeline
As always, I have include the source code to my project here. Please do bear in mind that I haven’t included any error handling or logging, so it’s not production-ready. However, it should provide you with a good head-start.
This posting is provided “AS IS” with no warranties, and confers no rights.