Fivetran Release Notes

We've expanded the list of supported regions in the dbt Cloud orchestration setup form and added a new Service Provider selector.Previously, only a limited set of regions were available. You can now choose from all current dbt Cloud regions, including cell-based regions that require an account prefix in the access URL.To update your dbt Cloud orchestration connection to use a different region:

1. In the Fivetran dashboard, click Transformations.
2. Click Manage projects.
3. In the transformation list, click the three dots on the right side of the relevant dbt Cloud project.
4. Click Edit connection settings.
5. Select your Service Provider and Region.
6. Click Save & Test.

We have changed the sync strategy for the following tables and their child tables. We now incrementally sync these tables instead of re-importing them during every sync:

• AUDIT_RECORD
• EVENT_ORCHESTRATION
• PAUSED_INCIDENT_REPORTING_ALERT
• SCHEDULE
• SLACK_DEDICATED_CHANNEL
• TEMPLATE

We have changed the re-import strategy for the following tables and their child tables. We now re-import them once a day to capture updates and deletes. Previously, we re-imported these tables during every sync.

• ADDON
• BUSINESS_SERVICE
• EXTENSION
• EXTENSION_SCHEMA
• INCIDENT_WORKFLOW
• LICENSE
• RULESET
• TAGS
• VENDOR

The Modify connection schema config endpoint now supports row filtering for individual tables.See the full list of changes below:

• Each table in a schema update request now accepts a row_filter field of type RowFilterUpdateRequest. Setting this field creates or replaces the row filter for that table; sending null deletes the existing row filter; omitting the field leaves the existing row filter unchanged.
• A row filter consists of a name (required), a description (required), and between 1 and 10 column_clauses. Each clause specifies a column (max 500 characters), a column_type, an operator, and a list of values (each value max 1,000 characters). All clauses are combined with a logical AND, so only rows satisfying every clause are synced to your destination.
• The Retrieve connection schema config response now includes a row_filtering_supported boolean at the top level. The field is true when the connector type supports row filtering. The field is false when the connector does not support row filtering. The field is omitted when row filtering information is not available. …

Effective August 5, 2026, we have improved Fivetran Teleport Sync change detection for nullable columns in SQL Server connections. New connections created on or after August 5, 2026, distinguish NULL values from non-NULL values when calculating row hashes, improving data consistency in your destination. Existing connections continue to use their current behavior.Effective August 7, 2026, we have improved change tracking (CT) accuracy for computed columns in SQL Server connections. New connections created on or after August 7, 2026, exclude non-persisted computed columns from CT syncs if they use nondeterministic expressions that return DATETIME or INTEGER values, such as GETDATE().Previously, CT syncs evaluated these expressions when processing historical changes. As a result, the synced value could differ from the value at the time of the change, causing incorrect data in your destination. Existing connections continue to use their current behavior.To resume syncing an excluded computed column, update it to use a deterministic expression.Effective August 20, 2026, we've improved change tracking (CT) history mode syncs for SQL Server connections. New connections created on or after August 20, 2026, handle temporarily unavailable transaction metadata without omitting affected rows.Previously, delays in the availability of SQL Server transaction metada…

We have added the following new columns to the tables below:

Table

Columns

ACCOUNT

email

ATTRIBUTE

category_name, flows_count, and team_ids

ATTRIBUTE_CATEGORY

name and attribute_count

CAMPAIGN

lists_sorting_criteria and dispositions

CASES

agent_name and update_at

DO_NOT_CALL_LIST

status and teams

DO_NOT_CALL_NUMBER

created_at and updated_at

GUARDIAN_CASE

hits, user_baseline, and pop_baseline

GUARDIAN_SESSION

support_access

RECORD_LIST

account_id, unique_identifier_type, and teams

USER_ATTRIBUTE

name and proficiency

WALLETS

product_name