Salesforce connector

This article explains how the Salesforce connector for DataGalaxy works.

This connector is available in the following modes:

Connector scope

The connector allows you to import the following metadata from Salesforce into a Relational source:

• Standard objects and custom objects

• References between objects

By default, the functional and technical label attributes are populated for the entire scope.

Additional attributes are also filled in depending on the technology and by type of object. To make them appear in DataGalaxy screens, it may be necessary to adapt the screens of the concerned objects. See this article to learn more about screen customization.

The following table details the objects and attributes retrieved, and their correspondences in DataGalaxy :

Configuration of a connection

The connector supports two Salesforce authentication flows. Choose one before configuring the connection.

⚠️ Important Security Notice (Deprecation of Username-Password Flow)

Salesforce is sunsetting and blocking the legacy Username-Password flow by default in newer environments to enforce stronger security standards. For details, refer to the official Salesforce Release Notes on Username-Password Flow Blocking.

All users are strongly encouraged to use the Client Credentials Flow to ensure service continuity and robust security.

Option 1: Client Credentials Flow (Recommended & Secure)

This modern authentication flow does not require storing individual user passwords or security tokens in the connector configuration.

To set up this flow, you must perform the following configuration steps in your Salesforce instance:

1. Configure a Client Credentials Flow.
   Follow the official Salesforce guide: Configure Client Credentials Flow for External Client Apps.
2. Assign a Run-As User: In the App's Policies, you must assign a Run-As User. Choose a user account with sufficient data access permissions for the objects DataGalaxy needs to scan.
3. Configure OAuth Scopes: In the App's OAuth Settings, you must add the Manage user data via APIs (api) OAuth scope to the app. Without it, Salesforce issues a token that cannot access the REST API.
4. Note your org's My Domain URL, for example https://acme.my.salesforce.com. This flow is not served from https://login.salesforce.com.

The following information is required to set up a connection using Client Credentials:

Option 2: Username-Password Flow 

For configuring a connection, you first have to enable user-password auth flow in your Salesforce instance, then create a Connected App (which may require to activate the creation of Connected Apps in the External Client Apps settings). This flow will require the user to get a secret token and his user and password, in addition to the client_id (consumer key) and client_secret (consumer secret) provided by the Connected App.

The following information is required to set up a connection:

The connector uses version 54.0 of the Salesforce REST API via a connected app. 

Execution of the connector

To create a connection to Salesforce via the Online connector, the entry points are as follows:

• From the Import button of the "Shortcuts" widget on the home screen of a client space or workspace 

• From the Import button of one of the modules when it is empty

• From the Import button in the contextual menu of one of the modules, on the right side of the filtered views

• From the Add a connection button in the Connector tab available in the workspace setup screen

You can optionally filter (by module, connector type or by using the search bar), then click on the desired technology: 

You then need to complete the login form using the login information described above to perform an import. For more details on the steps involved in running the Online connector, you can consult the following article: [HowTo] Running the Online Connector. 

This technology is also available via the Desktop Connector, you can find more information on the procedure here: [How to] How to use the connector.

Releases