The action logs will keep track of all communication between SurveyMonkey Apply and Salesforce. This article will walk through how to access your Action Logs and how to use them to interpret information.
- How to Access your Salesforce Action Logs
- Log Details
- How to Filter your Logs
- How to View Record Details
- Understanding the Event Description
- Access the Salesforce Integration section of the site
- Click the name of your Salesforce integration.
- Click View Logs at the top of the Integration
Within your log will be brief details on each record that occurred.
| Column | Description |
| # |
Each sync will be assigned a number that increments with each new sync. |
| Action |
The name of the Action that synced. |
| Action Type |
This column will display the whether the synced action was a Push or a Pull as well as the Mapping Event that occurred. There are three possible Mapping Events that can occur:
|
| Date |
The date and time that the sync. TIP! Click on the date to view more details on the record. For more information you can also refer to How to View Record Details. |
| Salesforce Object |
Based on the Action that was synced, this will display the applicable Salesforce Object Type. |
| Application |
This will display the Name of the Application as set in the Program's Settings |
| Applicant |
This will display the User that the application belongs to. |
| Details |
This column will display the status of the synced records. This column can also be referred to as the Event Description. The possible Event Descriptions are:
For more information in regards to this column you can refer to Understanding the Event Description. |
| Actions |
When the Action is Successful, you can click on the arrow icon to View Additional Record Details. When the Action is Unsuccessful, you can click on the rerun icon to rerun the single action. |
At the top of the log you will find various filters that can be applied to records of syncs that have occurred. Filters are applied by selecting one of the options within the status, objects, or mapping event criteria described below:
| Filter | Options |
| Action Types |
Filter your records based on whether the Action is a Push or Pull Action, or All Action Types. |
| All Salesforce Objects |
Filter your records based on the Salesforce Object Type linked to the Action. |
| Statuses |
Filter your records based on the statuses in the Event Description Column:
|
NOTE: In addition to filtering your records, you can also use the Search field, to search for the User or Application.
In addition to the brief Log Details described above, You can click on the Arrow icon under the far right column in order to view additional details on the record.
| Details |
A Salesforce Link and Salesforce ID will be provided for each successfully synced action to allow you to quickly view the record within your Salesforce. |
| Mapped Fields |
The Fields you are attempting to Sync will appear with the information that was updated to them. |
As mentioned above, the Sync Details, or Event Description, column will display important information on the status of the sync. The log itself will distinguish between successful, unsuccessful, and resolved transactions.
NOTE: The description displayed is dependent on the information that is provided to SM Apply by Salesforce.
| Status | Description |
| Successfully completed |
The transaction was successful. The sync did indeed happen, and all specified fields in the action have been synced. |
| Unsuccessful |
The transaction was NOT successful. Error details are shown to provide insight into what the issue was. Beside the error message is an option to rerun the single action. This gives you an opportunity to look at the error message, fix any errors either in the data or in the configuration, and rerun the action with the new data and configuration. For more information you can also refer to How to Troubleshoot an Unsuccessful Sync |
| Resolved |
If rerunning an error action is successful, the log item is marked as resolved. This allows you to be sure that the item is now successfully in Salesforce. |