Fivetran Release Notes

We have added the sync_type field to the sync_start and sync_end log events. The field identifies whether a sync is HISTORICAL or INCREMENTAL.

You can now select the Amazon Advertising profiles whose data you want to sync. To support this change, we have added an optional field, Profiles to sync, to the connection setup form. For more information, see our setup instructions and REST API documentation.

We've added the following new account-level and destination-level audit trail log events for Lake Compute personal access token to JWT token exchange:

• lake_compute_token_exchange: Logged when a personal access token is successfully exchanged for a JWT. Includes the token ID (jti), principal type, account ID, and destination ID.
• lake_compute_token_exchange_failed: Logged when token exchange fails. Includes the token ID (jti), account ID, destination ID, failure reason, and decision category.

These two new log events are available on the Enterprise plan or higher.

You can now select Advertiser Targeting, Campaign Targeting, and Ad Group Targeting as breakdown levels for custom reports, along with two new metrics: paid impressions and eCPM. These new targeting levels let you break down account-, campaign-, and ad group-level performance by targeting dimensions, giving you more flexibility to build granular custom reports.

We have renamed our Odoo connector, which uses the Synconics REST API module to sync Odoo data, to Odoo Synconics.

We have added the following new tables:

• PRODUCT_IMAGE_GROUP
• PRODUCT_IMAGE_GROUP_IMAGE
• PRODUCT_IMAGE_GROUP_VARIATION_ATTRIBUTE
• PRODUCT_IMAGE_GROUP_VARIATION_ATTRIBUTE_VALUE

We have added the following new locale-specific columns to the PRODUCT table:

• long_description_{locale}_markup
• long_description_{locale}_source
• short_description_{locale}_markup
• short_description_{locale}_source

We can now sync data from Zoho accounts hosted in the Canada region. To support this enhancement, we have added a Canada option to the Data Center drop-down menu in the connection setup form. For more information, see our setup instructions.

You can now check the status of asynchronous connection move operations using the Retrieve Move Connection Job Status (Beta) REST API endpoint. This endpoint allows you to monitor the progress of move jobs initiated with the CONTINUE_WITH_DATA sync behavior.

We support Active Data Guard as the source for the Binary Log Reader incremental sync method in Private Preview.We support physical standby databases in read-only mode only. However, we still need to connect to the primary database to manage directory objects. For more information about the required settings, see the Binary Log Reader setup instructions.

We now support reading change streams from secondary instances for Amazon DocumentDB versions 5.0 and above. We no longer require a connection to the primary instance to perform incremental updates on these versions. Versions below 5.0 only support change streams on the primary instance. For more information, see our Amazon DocumentDB Setup Guide.If you have an existing connection to an Amazon DocumentDB cluster running version 5.0 or above, and you have confirmed that Fivetran user can access change streams on the secondary instances, you can edit the connection details to connect to the secondary instances and sync from them.

The Connection Schema response now includes a new read-only parent_table field for tables that are grouped under a parent (core) table. The field contains the name of the parent table and only appears in the response for child tables. This allows API consumers, such as Terraform, to accurately reconcile schema configuration state.

We now preserve the zero-sentinel value 0000-00-00 00:00:00 in MySQL and MariaDB TIMESTAMP columns by changing the destination column type to STRING. Previously, we synced this value as NULL. If you enable type locking for your connection, we keep the existing column type and continue to sync the zero-sentinel value as NULL.This change affects connectors created on or after August 13, 2026.

We have upgraded the JDBC driver for the NetSuite SuiteAnalytics connector from version 8.10.184.0 to 8.10.190.0.

We now support syncing return data in presentment currency, allowing return amounts in the RETURN_OPEN_CLOSED_EXPIRED table to reflect the shopper’s local currency.

We have fixed an issue where columns with address data in the BUSINESS_PARTNER_ADDRESS table were synced as NULL even when valid data for these columns was available in SAP Business ByDesign. By default, we will update the data for this table in a subsequent sync, which will count towards free MAR.

We have added a new configuration option, Select all, to the Dimensions field in the connection setup form to allow you to select or deselect all available dimensions at once while configuring custom reports. For more information, see our setup instructions.