Fanatically Zen Support may need to temporarily enable debug logging in your CRM to capture more detailed information. These debug logs help our support team identify the root cause of the issue and offer a quicker resolution.
Follow the steps below to enable debug logging, reproduce the issue, and send us the necessary logs.
Step 1: Enable Debug Logging via Browser Console
Step 2: Reproduce the Issue
Step 3: Collect the System Logs
Step 4: Turn Off Debug Logging
Within SugarCRM
Step 1: Enable Debug Logging via Browser Console
From within your CRM, navigate to the Admin page and click Health Status under the Fanatical Zendesk header.
Right-click anywhere on the page and select Inspect (or press
Ctrl+Shift+Ion Windows /Cmd+Option+Ion Mac).Switch to the Console tab.
-
Paste the following command and press Enter:
SUGAR.App.api.call('get',SUGAR.App.api.buildURL('FanaticalZendesk/setting/logger/debug'),{},{});
Step 2: Reproduce the Issue
Reproduce the issue you're encountering. (The support team will provide guidance here, if needed. For example, if you're having trouble with a dashlet, navigate to the contact/target/lead/account and let the dashlet load. If you're having trouble with ticket syncing, navigate to Zendesk to edit a ticket and save it.)
Step 3: Collect the System Logs
Navigate back to Admin and click System Settings.
Scroll to the bottom and click View Log.
In the log viewer, click All at the top to display the complete log.
Copy all the log content and paste it into a
.txtfile.Attach this file in your reply to our support email.
Step 4: Turn Off Debug Logging
After you’ve collected and sent the logs, turn off debug logging to avoid unnecessary performance impact. In the Console tab of the browser, paste the following command:
SUGAR.App.api.call('get',SUGAR.App.api.buildURL('FanaticalZendesk/setting/logger/normal'),{},{});
Comments
0 comments
Article is closed for comments.