Deprecated Salesforce Extractor

In order to provide a better experience and support we are taking over the maintenance of Salesforce components from the 3rd party developer. Due to this, the original Salesforce (Bulk API) extractor (htns.ex-salesforce component) is being deprecated and replaced with the new Keboola maintained Salesforce extractor.

The old extractor configuration will continue to work, however you won’t be able to create new configurations. It is highly recommended to migrate to the new extractor version. We have recently added an option to perform most of the migration process automatically.

What’s new?

The new extractor comes with improved functionality:

  1. Improved dynamic UI

  2. Incremental fetching and primary key support

Now you have a better control of how the data is loaded. In the previous version users only had option to switch the `incremental` flag which caused addition of a hardcoded primary key. This caused issues with incremental loading of objects like *History which do not have an Id column at all. Now it is possible to define the primary key manually (defaults to Id) and choose between several options:

  • Full Load: Overwrite all data at destination

  • Incremental: Upsert data in destination

  • Incremental with Incremental fetching: Bring in only data that have changed since previous execution. The date column used for this comparison can be specified. This allows you to use for instance CreatedDate for History objects where the LastModifiedDate is not available.

  1. Fetch deleted records

Now it is possible to control whether to include also the deleted records

Migration process

We have released a migration script that will help you migrate any existing configurations directly from the project. 

Migration Behaviour:

  • Encrypted values (credentials) are NOT TRANSFERRED - because the component has a new ID users must set up credentials in the new configuration again manually.

  • Migration transfers component state so any incremental configurations will start from where they left off. 

  • The output bucket is maintained  - there is no need to change any downstream input mappings

  • Orchestrations are not updated - this step is left for the user so it can be done safely

Steps to migrate:

  1. Each affected configuration will display the following message:

  1. Click on the “PROCEED TO MIGRATION”

  2. You’ll be displayed a list of affected configurations and orchestrations:

  1. Click the “Migrate” button.

  2. After successful migration you will find all new configurations in your project

  3. Replace the credentials

  4. Inspect configurations and test if needed.

Change affected Orchestrations manually and replace the old configuration with the new one.