Salesforce Analytics connection
The Salesforce Analytics connection defines the user and the web service.
Connection tab
URL: Use Salesforce’s new endpoint. For production this should always be:
https://login.salesforce.com/services/Soap/u/<your_version_of_Salesforce>
Integrations using the older Salesforce URL continue to show the original configuration, but Salesforce redirects them automatically.
For OAuth2.0 Authentication:
The URL inserted in the Connection tab for OAuth 2.0 should be the instance URL.
Ex: <domain-instance-url>.my.salesforce.com/services/Soap/u/39.0
Authentication Type
Username-Password
-
User - The user name used to log into Salesforce. The user must have sufficient permissions to use the API and perform actions designated by your integration scenario.
-
Password - The password used to log into Salesforce. Older Salesforce passwords have been replaced by a combination of password and security token. Refer to the Salesforce connector topic for more information.
OAuth2.0
Prerequisites
- Salesforce CRM Analytics specific licensing for your Account
- Salesforce External Client App (or a legacy Connected App) configured with Client Credentials for OAuth 2.0 authentication.
- API access privileges confirmed by your Salesforce representative.
When OAuth 2.0 is selected as the Authentication Type, the following properties are displayed:
The URL inserted in the Connection tab for OAuth 2.0 should be the instance URL.
| Property | Help Text |
|---|---|
| Grant Type | OAuth 2.0 grant type to connect with your Salesforce External Client App (or legacy Connected App). (Displays one option only: Client Credentials.) |
| Client ID | Enter the Client ID from your Salesforce External Client App (or legacy Connected App). |
| Client Secret | Enter the Client Secret from your Salesforce External Client App (or legacy Connected App) |
| Access Token URL | Enter the Salesforce OAuth token endpoint. Eg: https://<mydomain>.my.salesforce.com/services/oauth2/token |
Test connection
You can test your connection settings before you use or save the connection in a process. The Test Connection ensures that your specified settings are correct, valid, and accessible. If the test connection is successful, you can save the connection. Otherwise, review and correct any incorrect settings, then test again.
You can only run the Test Connection against containers associated with your account (local runtimes, runtime clusters, and runtime clouds).
You can only run the Test Connection against containers associated with your account (local runtimes, runtime clusters, and runtime clouds).
