View Error logs for Work 365 Add-Ons
You may in rare cases run into some issues using our products. These issues might probably be caused due to a specific business process at your end, any updates/upgrades to the Dynamics 365 product.
To help debug, you can access detailed error logs for any issues with Work 365 Add-Ons.
If any server-side exception occurs with the Work 365 Add-Ons an error message is shown by default.
The below screenshot shows a sample error message from our ‘Record Clone’ product.
The error message screen may differ depending on the product installed.
In events such as these, detailed error logging should be available in the ‘Plugin Trace Log’ entity.
One would need “System Customizer” or ‘System Administrator’ role to access these logs.
Follow the below steps to access these error logs.
- Log in to the CRM system with a user having the above roles.
- Go to Settings ➤ Administration ➤ System Settings and open the ‘Customization’ tab
- Ensure the value in the ‘Enable logging to plug-in trace log’ is set to ‘All’ or ‘Exception’. Click the ‘Ok’ button
- Perform the action which was done on the Work 365 product again to regenerate the error.
Note: This step is only needed if the value in #2 above was set as ‘Off’ when the issue occurred
- Open ‘Advanced Find’ and look for ‘Plug-in Trace Logs’ entity.
Select ‘Type Name’ as a filter
Note: The value to be searched for ‘Type Name’ depends on the product installed. Use the table below identify the value you need
Work 365 Add-On Name ‘Type Name’ Value (to be searched) Record Clone IOTAP.AddOn.RecordClone2016.Clone Report Scheduler IOTAP.AddOn.ReportScheduler Email to Case Automation IOTAP.AddOn.EmailToCase
The screenshot below displays advanced find being used to search for ‘Record Clone’ logs
Click on ‘Results’
- On the results page, sort on the ‘Execution Start Time’ field to make sure the latest record displays first
The screenshot below shows the logs generated for our ‘Record Clone’ product.
- Open up the latest record and scroll down to the ‘Execution’ tab
- Copy the contents of the ‘Message Block’ and ‘Exception Details’ field and send it across to firstname.lastname@example.org.
Please do provide additional details with regards to what was the action performed, the entity involved and any other information as such which would help us to resolve the issue sooner.
- Ensure that you restore the settings in #2, back to its original value after you accessed the logs.