Clients often ask us to customize their CRM implementation beyond the original out of the box capabilities. There are many options you can use as a developer to eXtend CRM (xRM). For the sake of this blog, we'll focus on plugins; and in particular how to circumvent an issue when working with Plugin Profiler.
I was working on Dynamics CRM 2013 online version and was using Visual Studio 2012 developer tools for deployment in Dynamics CRM 2013. I created a plugin with the help of Visual Studio developer tools and had registered my plugin through the Visual Studio developer tools, which is a fast and easy process. When I was working with the plugin I was getting the unexpected error shown below in the execution of the plugin:
"”<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring xml:lang="en-US">Download the details and load with Plug-in Profiler.
I tried to investigate the exceptions to find out what the error was, but I was unable to figure it out. My code was running fine and there were no mistakes.Then I realized that earlier to debug my plugin I tried to use the plugin registration tool and in this process I executed profiling of the plugin. Debugging through the plugin registration tool was not successful because I was unable to generate log file, but in this process the plugin got profiled. I thought this error was happening because something was wrong with the profiling.
To resolve this error I removed the profiling from the plugin, and after removing the profiling I found the plugin to be working fine. Follow the steps below to remove profiling from your plugin if you are facing the same issue:
1. Run PluginRegistration.exe and connect Dynamics CRM instance with Plugin registration tool.
2. After clicking on Create New Connection fill in all the information and click on Login.
3. Once you are logged in, you will see all of the plugins which are registered under your organization.
4. To remove profiling from the plugin, click on uninstall profiler (this option is enabled once profiling for one of the plugins is completed).
5. Once I uninstalled the plugin profiler from the plugin, and deployed the plugin through Visual Studio developer tools, it started working fine.
Hope that this information is helpful for those who are developing plugins for Microsoft Dynamics CRM 2013 Online. For more information about this blog or C5 Insight, Contact Us.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.