As a developer, there quite a few times that you need to debug a plugin. Typically for doing that, you might have written some trace statements or you were planning to get the error logs and step through the code in Visual Studio.
One thing is common between the two. Both types of debugging need the error logs to be downloaded. There could be a few instances where you might not have gotten the error logs.
Let’s take a look at a couple of settings that need our attention.
- Make sure that the step is being profiled! We might be so caught up in the situation trying to resolve the issue that this might be forgotten.
- Ensure that the organization’s error logs’ settings are set to capture all details of error logs. To do that, click on Settings/Advanced Settings
Go to Settings/Administration/System Settings.
Click on the Customization tab.
Under plugin and custom workflow activity tracing, ensure the setting for “Enable logging to plug-in trace log is set to “All”. Once you selected that option, Click Ok.
A lot of the developers forget about the above settings change because, by default, the logging is set to off. We need to manually change it to “All” to enable the logging.
It is recommended to disable the capturing of logs in Prod (turn the above setting off) because it can prevent the unnecessary capture of error logs. If there is an issue, we can always replicate it in DEV/QA environments and capture the logs there.
Dynamics CRM is an exciting software and the possibilities with it are limitless. If you are interested to know more about the solution, do
Download our eBook “