Difference between revisions of "PEC-GPA/Current/Administrator/GplusTroubleshoot90"
(Published) |
|||
| Line 60: | Line 60: | ||
</ul> | </ul> | ||
|Status=Yes | |Status=Yes | ||
| + | }}{{Section | ||
| + | |anchor=BrowserLogs | ||
| + | |alignment=Vertical | ||
| + | |structuredtext={{NoteFormat|For troubleshooting purposes, Gplus Adapter writes the list of all agent level crm-adapter option settings to the browser log.|2}} | ||
| + | |Status=No | ||
}} | }} | ||
}} | }} | ||
Revision as of 13:57, March 23, 2022
Contents
If you are having issues with Gplus Adapter integration with Salesforce, you can try some of these solutions.
Expanded troubleshooting notifications
To configure troubleshooting and confirmation notifications, in the Agent Annex or Agent Group Annex, create the salesforce.debug-notifications key in the crm-adapter section and set the value to true.
Salesforce Client API saveLog() method error Notifications
To troubleshoot Salesforce Client API saveLog() method errors, Gplus Adapter can display notifications. To fix saveLog() method errors, validate your Salesforce configuration, and ensure that the interaction data matches your Salesforce configuration.
The following are examples of Salesforce error notifications when the Salesforce saveLog() method is called:Mismatch between the name of the field in custom field mapping and Salesforce field label for Activity object.
When interaction userData type does not match Salesforce object custom field data type.
When Salesforce Object validation rule formula results in an error.
