Release Notes

September 2026

The Data Models tab for Quickstart transformations now shows the status of dynamic models, Salesforce formula field models and Microsoft Dynamics 365 CRM models. Previously, these models always appeared as Active, even when Fivetran had automatically paused them after repeated failures.

The Status column now shows how many Quickstart data models are paused. Select the count to open a drawer that lists the paused models. Paused models stop updating, so views that depend on them may show outdated data.

To resume paused models, select Run full refresh in the drawer. The full refresh reruns the models, and they resume if they succeed.

Paused models in Quickstart data models

August 2026

v2.4.1

Feature Updates

Adds DuckDB as a supported destination.

v2.4.0

The account, campaign, contact, and opportunity daily history models, and their related variables, are not currently available in Quickstart.

Schema/Data Change (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`stg_salesforce__account_history` `stg_salesforce__contact_history` `stg_salesforce__opportunity_history`	Removed model			BREAKING: Run `--full-refresh` on the three daily history models after upgrading. `salesforce__account_daily_history`, `salesforce__contact_daily_history`, and `salesforce__opportunity_daily_history` now read directly from the `salesforce_history` sources, matching the `salesforce__campaign_daily_history` pattern

Bug Fix

Fixes an issue in salesforce__account_daily_history, salesforce__campaign_daily_history, salesforce__contact_daily_history, and salesforce__opportunity_daily_history where a record that remained current but hadn't changed recently could stop receiving new daily rows on incremental runs. Currently active records now continue to receive a daily row regardless of how recently they last changed. Requires --full-refresh to backfill any rows that were previously missing.

Feature Update

Adds a configurable lookback_window variable (default 1 day) to salesforce__account_daily_history, salesforce__campaign_daily_history, salesforce__contact_daily_history, and salesforce__opportunity_daily_history. Each incremental run now reprocesses the last lookback_window days in addition to any new dates, so a corrected or backfilled history record landing within that window is picked up automatically instead of requiring a --full-refresh.

July 2026

v2.3.0

Schema/Data Change

5 total changes • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`salesforce__campaign_performance`	New model	—	One row per campaign	Requires the `campaign` source table. Conditionally joins `campaign_member` and `record_type`.
`salesforce__campaign_daily_history`	New model	—	One row per campaign per day	Disabled by default. Requires Salesforce History Mode and `salesforce__campaign_history_enabled: true`.
`salesforce__opportunity_enhanced`	New column	—	`opportunity_record_type_name`	Conditionally populated when `salesforce__record_type_enabled: true`. Joins `record_type` filtered to `sobject_type = 'Opportunity'`.
`stg_salesforce__campaign` `stg_salesforce__campaign_member` `stg_salesforce__record_type`	New staging models			Upstream models of `salesforce__campaign_performance`.

Feature Update

Adds support for salesforce__campaign_pass_through_columns to pass custom campaign fields through to salesforce__campaign_performance. See the README for configuration details.

January 2026

v2.2.0

Documentation

Updates README with standardized Fivetran formatting.

Under the Hood

In the quickstart.yml file:
- Adds supported_vars for Quickstart UI customization.

August 2025

v2.0.0

Breaking Changes

Source Package Consolidation

Removed the dependency on the fivetran/salesforce_source package.
- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference fivetran/salesforce_source in your packages.yml, you must remove this dependency to avoid conflicts.
- Any source overrides referencing the fivetran/salesforce_source package will also need to be removed or updated to reference this package.
- Update any salesforce_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

dbt Fusion Compatibility Updates

Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all dbt_utils.unique_combination_of_columns tests.
- Moved loaded_at_field: _fivetran_synced under the config: block in src_salesforce.yml and src_salesforce_history.yml.

Under the Hood

Updated conditions in .github/workflows/auto-release.yml.
Added .github/workflows/generate-docs.yml.