Salesforce

Salesforce Environments

Salesforce allows businesses to create accounts in multiple environments, such as:

Production: This is the environment that holds live customer data and is used to actively run your business. A production org is identified by URLs starting with https://login.salesforce.com.
Sandbox: This is a copy of your production organization. You can create multiple sandbox environments for different purposes, such as development and testing. Working in the sandbox eliminates any risk of compromising your production data and applications. A sandbox is Identified by URLs starting with https://test.salesforce.com.

Prerequisites

An active Salesforce production account, or sandbox account.
History tracking is enabled to track history objects.

Configuring Salesforce as a Source

Perform the following steps to configure Salesforce as a Source in Hevo:

Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipeline List View.
In the Select Source Type page, select Salesforce.
In the Configure Your Salesforce Account page, click on + Add Salesforce Account or + Add Another Account (if an account already exists).
Select the environment from which Hevo must ingest the data, and then, click Continue.
Log in to your Salesforce account.
Click Allow to authorize Hevo to access your Salesforce Account.

You are then redirected to the Configure Your Salesforce Account page.
Specify the Pipeline Name, and then, click CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

Hevo loads all the objects linked with your Salesforce account.

Historical Data: Once you create the Pipeline, all data associated with the Salesforce account is ingested by Hevo and loaded into your Destination.

Incremental Data: Once the historical load is completed, all new and updated records are synchronized with your Destination.

Source Consideration

If any event is deleted in Salesforce, the ISDELETED column in Salesforce is marked TRUE. These deleted events do not appear in the Salesforce dashboard.
Now, when Hevo starts to replicate data from the Salesforce applications to your selected Destination, these deleted events which are marked TRUE in the ISDELETED column also get replicated to your Destination. As a result, you might see more events in your Destination than the Source.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

ER Diagram

Data Model

Hevo uses the following data model to ingest data from your Salesforce account:

Object	Description
Account	Represents information about the company or business user.
Campaign	Represents campaigns and tracks their efficiency with cost, revenue, and converted leads analysis.
Contact	Represents a company or a person associated with an account that can become a potential customer.
Event	Represents an event in the calendar.
Lead	Tracks valuable prospects apart from contacts, and convert them into opportunities.
Opportunity	Tracks and stores your deals in progress.
Product	Represents a product your company sells.
Custom Objects	Represents custom objects, entities that support custom objects, and their standard fields, named with a suffix `__c.`
StandardObjectNameShare	Represent a model for all share objects associated with standard objects.
StandardObjectNameHistory	Represent a model for all the history objects associated with standard objects.
StandardObjectNameOwnerSharingRule	Represent a model for all owner sharing rule objects associated with standard objects.
StandardObjectNameFeed	Represent a model for all the feed objects associated with standard objects.

Limitations

Hevo only supports the objects fetched using the Bulk API method.
Hevo does not fetch any files added as attachments in Salesforce.
Hevo does not fetch any columns of Compound data type.

Last updated on 07 Jan 2021