Skip to main content

Jet Analytics Salesforce Data Source

Use this provider to connect to your Salesforce data.

Configuration manual

Data Source

Connection settings

These settings relate to the connection to your Salesforce account and API configuration.

Domain

Enter the domain for your Salesforce solution.

API version

Specify the API version to connect to. The default value of v65.0 is the latest version available at the time this provider was developed.

Polling interval in seconds

When pulling data using the Bulk 2.0 API, the connector first creates a query job and then polls the job status until it completes before retrieving any data. For small tables this may be instant, but for larger tables (100k+ rows) increasing this interval is recommended. Each poll consumes one request from the request quota. There is a maximum of 10 polling attempts, so set the interval accordingly.

Max rows per batch

Optionally specify the number of rows returned per batch or page. The default uses the API default, which is based on total data size (2 GB at the time of release). No pagination occurs until data exceeds 2 GB, regardless of the number of rows.

Authentication settings

Authentication type

Select the authentication flow to use for authentication.

Client credential flow

This flow requires a Client ID/Key and a Client Secret. These can be found in the app settings within Salesforce where the connected app was created.

JWT Bearer token flow

This flow requires the following:

  • Client ID/Key
  • Username — the Salesforce user on whose behalf the token will be issued. This affects permissions and access.
  • Private key PEM — include the header and footer, as these identify the PEM key version.
  • Audience — typically https://login.salesforce.com. This is the endpoint where the token request is issued.

Salesforce settings

These settings control what data is read from Salesforce and how it is read.

Culture

Define the culture to use when reading data pulled from Salesforce. This can affect how decimals and datetimes are interpreted. In most cases this should be left blank.

Filter Salesforce objects

Salesforce returns a large number of objects, many of which are not relevant in a data warehouse context. Metadata calls also take longer the more objects are included. This setting applies a filter to reduce the object set returned. Objects that are filtered out are logged along with the reason.

The available filter options are:

  • Auto — The most restrictive filter. Filters based on several heuristics including feed, share, and platform events. For most use cases, this returns more than enough objects.
  • Comprehensive — Filters based on a whitelist of objects. Intended to be backwards-compatible with the objects returned by previous connectors.
  • Minimal — Applies only hard filters on objects that are not queryable or are system views.

Object exclusion patterns

Provide a list of objects or patterns to exclude from your metadata call. Use this for objects you know you do not need.

Object inclusion patterns

Provide a list of objects or patterns to include in your metadata call. Use this when you know exactly which objects you need from Salesforce. When combined with Use only object inclusion patterns, only the specified objects are retrieved, saving time and reducing the number of queries made to Salesforce during the metadata call.

Use only object inclusion patterns

When enabled, only the objects or patterns specified in Object inclusion patterns are used to retrieve metadata from Salesforce. If you know exactly which tables you need, this is the fastest approach.

Filter scope

Adds an additional WHERE clause to table queries to filter results by the current user and the selected scope. The available options are:

  • None
  • Delegated
  • Everything
  • Mine
  • Mine and my groups
  • My territory
  • My team territory
  • Team

Archive mode

When enabled, deleted records are included in the query results.

Skip formula fields

When enabled, composite (formula) columns are excluded from query results.

Use display names

When enabled, tables and columns use the metadata label (display name) rather than the object's actual API name.

Was this article helpful?

We're sorry to hear that.