User Permissions Needed: Account Administrator
Salesforce is highly customizable and allows you to create complex logic and processes based on your needs. As processes get executed, errors can come in different forms and can be challenging to address. This is where Salesforce's Debug Logs feature shines and helps us to identify the root cause of problems.
Any Salesforce Administrator can enable and access logs, but we strongly recommend that the installer of the Mavenlink for Salesforce package do so, in order to avoid any user permission issues during the debug process.
How to Enable Logging
- Log into your Salesforce account.
- Navigate to the Mavenlink Configuration > Integration Options subtab.
- Navigate to Logging Settings at the bottom of the page, and click Edit.
- Update settings to:
- Logging Status - Internal
- Logging Level - 9
- Log Entry Longevity - 2
- Click Save.
- Test the logging function by re-performing actions, such as making updates to projects or opportunities that you are having issues with. The actions should now be recorded and accessible through the Reports tab.
During testing, it's best practice to check the status of actions performed before looking at them in the Reports.
How to Check Action Statuses
- Navigate to Setup in the upper right-hand corner of the interface.
- Search for "apex jobs" in the left-hand Quick Find box.
- Click on the Apex Jobs in the search results. A list of performed actions and their details are displayed in a table.
- Look for the actions you just performed. If they have not been recorded, please contact Support.
Mavenlink Log Report
How to View Mavenlink Debug Log Reports
Access pre-built reports that are bundled with the integration.
- Open the Reports tab.
- If the tab has not been added yet, click on the plus (“ ”) icon.
- Select Reports.
- Open the Mavenlink Reports (Installed Package: Mavenlink for Salesforce) folder, and click on Mavenlink Log Entries.
- All log entries are displayed, and can be exported to an Excel or CSV file for filtering and sorting. To export, click on Export Details.
- Leave Export File Encoding as is.
- Select whether you want the report in an Excel or CSV format.
- Click Export.The file opens. The report can be reviewed or sent to our Support team for further investigation.
It's a good idea to disable debug logs again after exporting the ones you need, as Salesforce has Data Storage Limits, and logging consumes significant storage.
How to Disable & Delete Mavenlink Debug Logs in Salesforce
- Navigate to your profile, and click Developer Console.
- Navigate to Debug Open Execute Anonymous Window, and click Open Execute Anonymous Window.
- Enter this Apex Code and click Execute:
List<mavenlink__Mavenlink_Log__c> deleteRecords= [select id from mavenlink__Mavenlink_Log__c limit 10000]; delete deleteRecords;
In the bottom panel of the window, the Status returned for the operation should be "Success". This means Mavenlink Debug Logs are deleted and disabled now.
If you're having difficulty debugging an issue, please contact Kantata Support to submit a ticket with the exported log reports.
- Salesforce Overview
- Salesforce Field Mappings
- Salesforce Integration Setup
- Salesforce Advanced Integration
- Creating a Salesforce Account for Testing
- Mapping Salesforce Opportunity Stages to Mavenlink Project Statuses