Salesforce

Salesforce is a cloud computing Service as a Software (SaaS) company that allows you to use cloud technology to connect more effectively with customers, partners, and potential customers.

Hevo uses Salesforce’s Bulk API to replicate the data from your Salesforce applications to the Destination database or data warehouse. To enable this, you need to authorize Hevo to access data from the relevant Salesforce environment.

Salesforce Environments

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

• Production: This environment holds live customer data and is used to actively run your business. A production organization 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 one for development and another for testing. Working in the sandbox eliminates risk of compromising your production data and applications. A sandbox is identified by URLs starting with https://test.salesforce.com.

---

Source Considerations

• Derived fields (or calculated fields) are fields that derive their value from other fields or formulas. Derived fields are not updated in the Destination during incremental loads even if their value changes due to a change in the formula or the original field.

  In Salesforce, whenever any change occurs in an object, its SystemModStamp timestamp field is updated. Hevo uses this SystemModStamp field to identify Events for incremental ingestion. In case of derived fields, a change in the formula or the original field does not affect the object’s SystemModStamp value even though the derived field’s value may change. Due to this, such objects are not picked up in the incremental load. However, if another field in the object is updated alongside, then the incremental load picks up the derived field updates also.

  As a workaround, Hevo runs the historical load every 20 days by default for objects containing derived fields. You can contact Hevo Support to change this historical load frequency. You can also restart the historical load for the object manually. If the object was created after Pipeline creation, you need to restart the historical load at the Pipeline level.

• Hevo cannot ingest incremental data for back-dated records, as Salesforce does not update the SystemModStamp column for these records. Hevo uses this column to identify Events for incremental ingestion.

  As a workaround, you can restart the historical load for the object.

• Some Salesforce objects, such as EntityDefinition, do not contain the SystemModStamp timestamp field. As a result, Hevo cannot capture data changes for such objects and marks them as Full Load objects. For these objects, Hevo replicates the entire dataset in each ingestion. Additionally, Hevo cannot differentiate between historical and incremental data, so all consumed Events are marked as billable.

• The SystemModStamp timestamp field tracks changes made to the entire object, rather than individual columns within a record. Hence, even if you skip the frequently updated columns for an object from the Schema Mapper, Hevo picks up the object for ingestion if its SystemModStamp timestamp field has changed since the last ingestion.

• There may be a data count mismatch at the Destination due to records deleted in your Salesforce account. When a record from a replicable object is deleted in Salesforce, the IsDeleted column for it is set to True. Salesforce moves the deleted records to the Salesforce Recycle Bin, and they are not displayed in the Salesforce dashboard. Now, when Hevo starts the data replication from your Source, using either the Bulk APIs or REST APIs, it also replicates data from the Salesforce Recycle Bin to your Destination. As a result, you might see more Events in your Destination than in the Source.

• If you pause a Pipeline for more than 15 days, Hevo cannot replicate the deleted data, if any, to your Destination. This is because Salesforce retains deleted data in its Recycle Bin for 15 days. Also, Salesforce purges the oldest records in the Recycle Bin every two hours if their count exceeds the limit for your organization. The record limit is 25 times your organization’s storage capacity. Therefore, to correctly capture the deleted data, you must run the Pipeline within two hours of deleting the data in Salesforce.

• The maximum number of Events that can be ingested per day is calculated based on your organization’s quota of batches.

  Suppose your organization is allocated a daily quota of 15000 batches per 24 hours, and each batch can contain a maximum of 10000 Events.

  Then, the daily Event consumption is calculated as follows:

  • The number of batches created per Object (X) = Number of Events for the Object/10000.

    Note: This value, X is rounded off to the next integer.

  • And,

    The total number of batches created across all Objects in the Pipeline (Y) = Sum of the number of batches created for each Object (ΣX).

    This number, Y is the number of batches that are submitted in one run of the Pipeline. This number may vary in each run of the Pipeline and is calculated as follows:

    The number of Pipeline runs in a day (Z) = 24/Ingestion frequency (in hours).

    The number of batches that can be submitted in a day = 15000

    Therefore,

    The maximum number of batches that can be submitted in one run of the Pipeline = 15000/Z.

  Example:

  Suppose you have two Objects containing 55800 and 25000 Events respectively, and the ingestion frequency is 12 hours. Then,

  The number of batches created for Object 1 (X1) = 55800/10000 = 5.58.

  Therefore, six batches are created; five with 10000 Events each and the sixth with 5800 Events.

  The number of batches created for Object 2 (X2) = 25000/10000 = 2.5.

  Therefore, three batches are created; two with 10000 Events each and the third with 5000 Events.

  The total number of batches created across all Objects in the Pipeline (Y) = X1 + X2 = 6 + 3 = 9.

  These nine batches are submitted in one run of the Pipeline.

  Now, as the Ingestion frequency is 12 hours,

  The total number of Pipeline runs in 24 hours (Z) = 24/12 = 2.

  And,

  The maximum number of batches that can be submitted in one run of the Pipeline = 15000/2 = 7500.

  Here, against the available limit of 7500 batches per Pipeline run, only 9 batches are being submitted.

  Therefore, as long as Z x Y <= 15000, you are within the daily prescribed quota.

---

Limitations

• Hevo does not fetch any columns of Compound data type.

• It is not possible to avoid loading the deleted data. Hevo loads the new, updated, and deleted data from your Salesforce account.

• Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.

• Hevo does not capture records permanently deleted from Salesforce. Permanent deletion removes records without moving them to the Salesforce recycle bin. As a result, if a record is deleted after the ingestion, it still shows in the Destination. If you do not want to retain the deleted data in the Destination, you can truncate the affected Destination tables and manually restart the historical load for the corresponding Source objects.

---

See Also

• Troubleshooting Salesforce

• Overview of Salesforce Objects and Fields

• Salesforce Developer Limits and Allocations

---

Revision History