We have upgraded our Salesforce connector to the Salesforce BULK API 2.0 version. The connector now uses both the Salesforce BULK API and REST API for incremental syncs. Previously, the connector used the REST API for incremental syncs. We are gradually rolling out the Bulk API feature to all our customers. Your user experience may vary depending on the implementation status. Contact our support team to enable this feature on your connector.
We now support the
IsArchived field. We are gradually rolling out this improvement to all existing customers. If you’d like to sync the
IsArchived field, contact our support team.
We now convert empty strings (
null objects. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.
We have upgraded our Salesforce connector from version 50.0 to 53.0 of the Salesforce REST API. We have added support for the AuthorizationFormTextFeed object. We have removed support for the AppleDomainVerification object. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.
We have fixed a bug where deleted records were missing from the OpportunitySplit object and were not being synced from Salesforce’s Get Deleted endpoint. We will re-import the OpportunitySplit object based on our re-import logic. We are gradually rolling out this improvement to all existing customers. The re-imported OpportunitySplit object will count towards your monthly active rows. If you observe that deleted records are not marked as deleted in the OpportunitySplit object, contact our support team.
We now sync the following system tables by default and have removed them from the Schema tab on your connector details page:
We now support the following Salesforce objects:
If you’d like to enable the feature on your connector, contact our support team.
We have upgraded our Salesforce connector from version 45.0 to 50.0 of the Salesforce REST API. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.
We now use Salesforce’s Bulk API 2.0 for your connector’s historical syncs. Previously, we used the REST API for the historical syncs. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.
You can now select the
FIVETRAN_FORMULA_HISTORY tables to sync from the Schema tab on your connector details page. We are gradually rolling out this new feature to all existing customers. If you’d like to enable this feature on your connector, contact our support team.
We have released Fivetran history mode for Salesforce. You can turn on history mode for any table and capture every version of each record in your destination. With history mode, you can analyze data from a particular point in time or analyze how data has changed over time. To learn more, read our history mode documentation.
We are gradually rolling out history mode to existing customers. If you’d like to access history mode immediately, contact our support team.
We have released pre-built, dbt Core-compatible data models for Salesforce. Find the models in Fivetran’s dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
We now capture deletes of history tables using the
is_deleted field from Salesforce.
Read our History tables documentation for more information.
We have disabled History mode for Salesforce history tables because history tables track object history by default. The changes made to an object over time are recorded in the Salesforce history tables using field history tracking.
We no longer capture deletes for tables with names ending with
_HISTORY, for example,
OBJECT_NAME_HISTORY. Deletes from these tables contributed an unacceptably high amount of monthly active rows.
You can now select the
FIVETRAN_QUERY tables to sync from the Schema tab on your connector details page.
We now add a fivetran_synced column while syncing empty tables and columns from the source.
We can now re-import tables that can’t be incrementally updated. We automatically detect tables with
replicateable = false and
updateable = false values and re-import them in full. We mark the re-imported tables as
notRecommended in the dashboard and exclude them from incremental syncs by default. However, you can choose to include them.
We now force the creation of schemas, even if they contain no data. This is especially helpful for Looker users since Looker’s pre-built SQL queries fail if all tables and columns in a schema are not present. Previously, we did not create schemas when they contained no data.
Even if a column is not populated in the source, we create a column for it in the destination with null records.
Note: We will not create a column if you have not selected it in the column config.
We are rolling out this improvement in a phased manner to ensure connector reliability. It may not be available to every customer right away. Contact our support team if you’d like to be included in the early phase of the rollout.
We have upgraded our Salesforce connector from Salesforce API version 41.0 to 45.0. The upgrade supports new objects available in Salesforce API 45.0. We will roll out the new version of our connector to all customers gradually over 3 months starting on July 12th.
- You can now configure your Salesforce connector through the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.
- Fivetran will add a log message to Customer Logs when skipping an infrequently updated table.
System columns, like
SystemModstamp, can no longer be excluded in column configuration.
We have upgraded the Salesforce API to v41.