August 2026
Managed Data Lake Service
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the data lake, which could cause differences between the source and destination data.
Schema changes
Braze
We have added two new tables, CAMPAIGN_ANALYTICS and CAMPAIGN_ANALYTICS_VARIATION.
Canvas Data 2 by Instructure
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
QUIZ_QUESTION | |||||
| column | New Column | question_data_matching_answer_incorrect_matches | |||
| column | New Column | question_data_neutral_comments | |||
| column | New Column | question_data_regrade_option | |||
| column | New Column | question_data_text_after_answers | |||
HubSpot
We have added the following new tables to sync data for the Courses object:
COURSECOURSE_COMPANYCOURSE_CONTACTCOURSE_DEALCOURSE_ENGAGEMENTCOURSE_PIPELINECOURSE_PIPELINE_STAGECOURSE_PROJECTCOURSE_PROPERTY_HISTORYCOURSE_TICKET
We are gradually rolling out this change to all connections.
SAP Concur
We have added a new column, report_id, to the ITEMIZATION table.
Improvements
BigQuery destination
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
Databricks destination
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
We have added a new feature, File source. You can now define a regex pattern to sync the attachments associated with your email. To support this feature, we have made the following changes to the connection setup form:
- Added a new option , File source, that allows you to choose between Attachment and URL in email body.
- Added a new field, URL link pattern, that allows you to sync files linked in the email body.
For more information, see our setup instructions
We are gradually rolling out this change to all existing connections.
Healthie
We have changed our sync strategy for the FORM_ANSWER_GROUP table. We now incrementally sync this table and use a 7-day lookback window to capture delayed updates.
JSON Double Quotes
Effective August 14, 2026, we have improved Fivetran replication for JSON scalar values for all connections. New connections created on or after August 14, 2026, will no longer persist these values with quotes (unless they are strings) in destinations, improving data consistency. Existing connections continue to use their current behavior.
Microsoft Advertising
We updated how we process the view_through_revenue column. Microsoft Advertising returns these values with a comma as a thousands separator (for example, 1,013.99). We now remove the separator and store the values as plain numbers (for example, 1013.99) for consistency with the connector's other metric columns.
This change applies to data synced going forward. If you rely on the previous formatting, update any downstream logic accordingly.
MongoDB
We no longer support the oplog incremental update method. If your connection was using the oplog incremental update method, syncs will no longer work.
MySQL
If a DATE or DATETIME column contains a value that isn't a valid date or datetime (for example, a zero date like 0000-00-00), we now preserve the original value by promoting the column to STRING instead of syncing it as NULL.
If you have type locking enabled on a connection, this promotion doesn't happen — invalid values are synced as NULL instead, and the column keeps its original type.
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.
MySQL destination
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
PagerDuty
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_RECORDEVENT_ORCHESTRATIONPAUSED_INCIDENT_REPORTING_ALERTSCHEDULESLACK_DEDICATED_CHANNELTEMPLATE
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.
ADDONBUSINESS_SERVICEEXTENSIONEXTENSION_SCHEMAINCIDENT_WORKFLOWLICENSERULESETTAGSVENDOR
Snowflake destination
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.
SQL Server
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.
SQL Server destination
All new connections set up on or after August 5, 2026 preserve null byte characters in string values. Previously, we removed null byte characters before writing string values to the destination, which could cause differences between the source and destination data.