Salesforce Einstein Analytics Connector¶
The Jitterbit Harmony Salesforce Einstein Analytics Connector establishes access to Salesforce CRM Analytics.
The Salesforce Einstein Analytics connector provides an interface for creating a Salesforce Einstein Analytics connection, the foundation used for generating instances of Salesforce Einstein Analytics activities. These activities, once configured, interact with Salesforce CRM Analytics through the connection.
The Salesforce Einstein Analytics connector is accessed from the design component palette's Connections tab (see Design Component Palette).
Salesforce Einstein Analytics is the former name for Salesforce CRM Analytics.
This connector is used to first configure a Salesforce Einstein Analytics connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
Together, a specific Salesforce Einstein Analytics connection and its activities are referred to as a Salesforce Einstein Analytics endpoint:
- Load: Uploads object data into Salesforce CRM Analytics and is intended to be used as a target in an operation.
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
Prerequisites and Supported API Versions¶
The Salesforce Einstein Analytics connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
The Salesforce Einstein Analytics connector uses the Salesforce SOAP API. Refer to Overview of Salesforce Objects and Fields in the Salesforce documentation for information on the schema nodes and fields.
If you experience issues with the Salesforce Einstein Analytics connector, these troubleshooting steps are recommended:
Ensure the Salesforce Einstein Analytics connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.verbose.logging.analytics" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.