Debugging a sandboxed plugin in CRM 2013 online may appear just a little obscure initially but not deny that it would be really life saver. Maybe you’ve given up the idea and instead decided to do something which i call poor man’s debugging – throwing InvalidPluginExecutionExceptions everywhere and hoping to find a remedy? I admit, I i did so that many too but this is merely wrong. Throwing exceptions is not just a solution for debugging, it is solution for handling exceptions and should stay that way. In this website post I’m teaching you, detail by detail, how you can debug a plugin in CRM and save plenty of commitment in the foreseeable future.
First we go through what you’ll need. You probably own all necessary components because you are a CRM programmer already. Then I explain an example scenario that I’m using while going right through this debuggin process. You might now close all other tabs in your web browser. This website post contains all you have to to be able to debug a plugin in CRM Online.
Let’s pretend we are creating a plugin that has to generate a contact address for a contact. We’ve created a plugin which will be fired always when a contact is created or updated (running a plugin on every revise is not preferred in this case but just play along). Both steps are authorized on pre-operation stage of execution.
- Advertising in your area
- How will she spend her weekends and holidays