September 2026
Schema changes
Freshdesk
We have added the following new tables:
SOLUTION_ARTICLESSOLUTION_CATEGORYSOLUTION_FOLDER
Google Ads
We have a new column, ai_max_ad_group_setting_disable_search_term_matching, to the AD_GROUP_HISTORY table.
Navan
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
BOOKING | |||||
| column | New Column | airline_route | |||
| column | New Column | confirmation_number | |||
| column | New Column | fare_basis_code | |||
| column | New Column | flown_cabin_class | |||
| column | New Column | gsa_rate | |||
| column | New Column | handling_fee | |||
| column | New Column | hotel_latitude | |||
| column | New Column | hotel_longitude | |||
| column | New Column | invitation_type | |||
| column | New Column | invite_connection_method | |||
| column | New Column | invoice_collection_fee | |||
| column | New Column | invoice_number | |||
| column | New Column | logged_as_user_name | |||
| column | New Column | route_type | |||
| column | New Column | transaction_fee | |||
BOOKING_BOOKER_HR_ATTRIBUTE_VALUE | |||||
| table | New Table | BOOKING_BOOKER_HR_ATTRIBUTE_VALUE | |||
BOOKING_PASSENGER_HR_ATTRIBUTE_VALUE | |||||
| table | New Table | BOOKING_PASSENGER_HR_ATTRIBUTE_VALUE | |||
BOOKING_PRICE_BENCHMARK | |||||
| table | New Table | BOOKING_PRICE_BENCHMARK | |||
BOOKING_SEGMENT | |||||
| column | New Column | fare_class | |||
Reddit Ads
We have added a new column, optimization_goal, to the AD_GROUP table.
Shopify
We have added the following new tables:
DRAFT_ORDER_PAYMENT_SCHEDULEDRAFT_ORDER_PAYMENT_TERMINVENTORY_TRANSFERINVENTORY_TRANSFER_LINE_ITEMORDER_LINE_DUTYORDER_LINE_DUTY_TAX_LINEORDER_PAYMENT_SCHEDULEORDER_PAYMENT_TERMTRANSLATABLE_RESOURCETRANSLATABLE_RESOURCE_TRANSLATABLE_CONTENTTRANSLATABLE_RESOURCE_TRANSLATION
Snapchat Ads
We've added a new column, url_macro_parameters, to the CREATIVE_HISTORY table.
Square
We have made the following changes to the ORDER_FULFILLMENT table:
- Changed the primary key from
_fivetran_idtouid - Added the following new columns:
shipment_detail_cancel_reasonshipment_detail_canceled_atshipment_detail_carriershipment_detail_expected_shipped_atshipment_detail_failed_atshipment_detail_failure_reasonshipment_detail_in_progress_atshipment_detail_packaged_atshipment_detail_placed_atshipment_detail_recipient_address_address_line_1shipment_detail_recipient_address_address_line_2shipment_detail_recipient_address_address_line_3shipment_detail_recipient_address_administrative_district_level_1shipment_detail_recipient_address_administrative_district_level_2shipment_detail_recipient_address_administrative_district_level_3shipment_detail_recipient_address_countryshipment_detail_recipient_address_first_nameshipment_detail_recipient_address_last_nameshipment_detail_recipient_address_localityshipment_detail_recipient_address_organizationshipment_detail_recipient_address_postal_codeshipment_detail_recipient_address_sublocalityshipment_detail_recipient_address_sublocality_2shipment_detail_recipient_address_sublocality_3shipment_detail_recipient_customer_idshipment_detail_recipient_display_nameshipment_detail_recipient_email_addressshipment_detail_recipient_phone_numbershipment_detail_shipped_atshipment_detail_shipping_noteshipment_detail_shipping_typeshipment_detail_tracking_numbershipment_detail_tracking_url
We will re-sync the ORDER_FULFILLMENT table at no additional cost to apply the new primary key and backfill historical data for the new columns. Be sure to update your downstream queries to align with these changes. Failing to do so may lead to missing or incomplete data in your data pipelines.
TestRail
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
GLOBAL_USER | |||||
| table | New Table | GLOBAL_USER | |||
GLOBAL_USER_ASSIGNED_PROJECT | |||||
| table | New Table | GLOBAL_USER_ASSIGNED_PROJECT | |||
PLAN_RUN | |||||
| table | New Table | PLAN_RUN | |||
PLAN_RUN_CONFIG | |||||
| table | New Table | PLAN_RUN_CONFIG | |||
TikTok Ads
We have added three new columns, campaign_name, adgroup_name, and campaign_automation_type, to the AD_HISTORY table. We have added the following new columns to the AD_HISTORY table:
adgroup_namecampaign_automation_typecampaign_name
Vonage Contact Center
| Table/column | Change type | Old name | New name | Notes | |
|---|---|---|---|---|---|
CONTENT | |||||
| table | New Table | CONTENT | |||
INTERACTION_CATEGORY | |||||
| table | New Table | INTERACTION_CATEGORY | |||
INTERACTION_CONTENT | |||||
| table | New Table | INTERACTION_CONTENT | |||
INTERACTION_HANDLING_AGENT | |||||
| table | New Table | INTERACTION_HANDLING_AGENT | |||
INTERACTION_SENTIMENT_DISTRIBUTION | |||||
| table | New Table | INTERACTION_SENTIMENT_DISTRIBUTION | |||
INTERACTION_SUB_CATEGORY | |||||
| table | New Table | INTERACTION_SUB_CATEGORY | |||
INTERACTION_TRANSCRIPT | |||||
| table | New Table | INTERACTION_TRANSCRIPT | |||
Improvements
AppsFlyer
We now support table-level resyncs for the AppsFlyer connector. You can trigger a resync for an individual table without affecting the sync progress of other tables.
Azure Blob Storage
We have added a new configuration option, Private Key Passphrase, to support Client certificate authentication using encrypted private keys. For more information, see our setup instructions and REST API Configuration.
BigQuery destination
BigQuery destinations now support column names that contain characters unsupported by Avro, such as column names that start with a number. Previously, Fivetran excluded these columns from syncs. To backfill historical data for these newly supported columns, re-sync your connections. We are gradually rolling out this change to all existing destinations.
We have improved how Fivetran handles large rows in BigQuery. We now evaluate the total row size before applying column-level limits. If the row is under approximately 100 MB, we sync the full values without truncation. If the row exceeds approximately 100 MB, we apply an 8 MB limit to each variable-length column (STRING, JSON, BINARY, and XML) to help reduce the row size.
Previously, we applied the 8 MB per-column limit regardless of the total row size. This change allows tables with fewer columns to sync larger individual values while staying within BigQuery row size limits.
Row filtering support for Float, Double, and BigDecimal data types
Row filtering now supports the Float, Double, and BigDecimal data types. You can enter values in standard decimal notation (1.23, -0.005) or scientific notation (1.23e-4, -4.5e10), and use these types with all supported operators, including In.
Float and Double values must fall within their respective IEEE 754 range limits. BigDecimal values are stored and compared as arbitrary-precision decimals with no enforced range limit.
For more information, see our row filtering documentation.
S3-Compatible Storage
The S3-Compatible Storage connector is now generally available.
Read our S3-Compatible Storage connector documentation.
SharePoint
We have added a new configuration option, Private Key Passphrase, to support Client certificate authentication using encrypted private keys. For more information, see our setup instructions and REST API Configuration.
Workday RaaS
Our Workday RaaS connector now supports a new query mode, WQL. WQL queries fetch report data in paginated ranges, allowing us to sync large reports incrementally without exceeding Workday's report size limit. To support this query mode, we have added the following fields to the connection setup form:
- Query Mode
- WQL QUERY
- Enable Incremental Filter
- Select Report Incremental Date Field
- Select incremental start date