Given that the server processes are not accessible when using Dynamics 365 online, debugging your server-side customization can be a bit trickier. In the past, we used to rely on custom log tracing to debug a plugin. We also had the option of using the plugin profiler to replay a defect in a development environment. However, with Dynamics CRM 2016, a new debugging technique was introduced.
In this recipe, we will explain how you can debug a Dynamics 365 online plugin using the online plugin and custom workflow activity trace log.
In order to trace your custom plugin or workflow activity, you will need to ensure that the correct tracing level is enabled in the system settings.
In order to change the level, navigate to the Settings | Administration | System Settings | Customization tab and level to Exception or All, as per the following screenshot:
You will also need a plugin or custom workflow activity to run.