Fivetran Release Notes

We have made the following changes to the ORDER_FULFILLMENT table:

• Changed the primary key from _fivetran_id to uid
• Added the following new columns:
  • shipment_detail_cancel_reason
  • shipment_detail_canceled_at
  • shipment_detail_carrier
  • shipment_detail_expected_shipped_at
  • shipment_detail_failed_at
  • shipment_detail_failure_reason
  • shipment_detail_in_progress_at
  • shipment_detail_packaged_at
  • shipment_detail_placed_at
  • shipment_detail_recipient_address_address_line_1
  • shipment_detail_recipient_address_address_line_2
  • shipment_detail_recipient_address_address_line_3
  • shipment_detail_recipient_address_administrative_district_level_1
  • shipment_detail_recipient_address_administrative_district_level_2
  • shipment_detail_recipient_address_administrative_district_level_3
  • shipment_detail_recipient_address_country
  • shipment_detail_recipient_address_first_name
  • shipment_detail_recipient_address_last_name
  • shipment_detail_recipient_address_locality
  • shipment_detail_recipient_address_organization
  • shipment_detail_recipient_address_postal_code
  • shipment_detail_recipient_address_sublocality
  • shipment_detail_recipient_address_sublocality_2
  • shipment_detail_recipient_address_sublocality_3
  • shipment_detail_recipient_customer_id …

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.

All new connections set up on or after August 28, 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 made the following changes for all new connections set up on or after August 18, 2026:

• We now preserve NaN and Infinity values in non-primary-key FLOAT and DOUBLE columns instead of syncing them as NULL values. Primary key columns still require valid, non-NaN values.
• We now preserve the sign of negative zero (-0.0) instead of normalizing it to 0.0.

We now support using Managed Data Lake Service as the storage layer for Snowflake destinations, allowing you to store your data as Apache Iceberg™ tables in a Fivetran-managed data lake and query those tables from Snowflake. This feature is available for SaaS Deployment only and is currently in beta.To support this feature, we have added the following fields to the Snowflake destination setup form:

• Table Type: Allows you to select how Fivetran stores the destination data, either in native Snowflake tables or as Iceberg tables in an associated Managed Data Lake Service destination.
• Storage Configuration: Allows you to select an existing Managed Data Lake Service destination to use as the storage layer or create a new data lake. …

v1.8.0

Schema/Data Change

1 total change • 1 possible breaking change

Data Model(s)

Change type

Old

New

Notes

stg_netsuite2__accounting_book_subsidiaries
stg_netsuite2__accounting_book_subsidiaries_tmp

Removed model

Deprecated in v0.9.0 and unused in downstream models. Now fully sunset.

Feature Update

• Adds the transaction_accounting_lines_pass_through_columns variable, persisting chosen custom columns from the TRANSACTION_ACCOUNTING_LINE source table. These fields are brought into netsuite2__transaction_details. For more details, refer to the Passing Through Additional Fields section of the README.

Bug Fix

• Fixes null conversion amounts for top-level subsidiaries missing a self-conversion exchange rate; rate now defaults to 1. Updates converted_amount values in netsuite2__transaction_details, netsuite2__income_statement, and netsuite2__balance_sheet.

Note: A --full-refresh is recommended after upgrading.

We have added the following new columns to the QUOTE_REQUEST table:

• created_at
• currency_id
• negotiated_savings
• negotiated_savings_currency_id
• original_id
• planned_savings
• planned_savings_currency_id
• public
• state

We have added a new column, participation, to the QUOTE_SUPPLIER table.We have added the following new columns to the CONTRACT table:

• contract_parties_field_container_id
• contract_parties_field_container_created_at
• contract_parties_field_container_updated_at
• contract_parties_field_container_custom_fields
• contract_parties_field_container_contract_type_custom_field_1
• contract_parties_field_container_contract_type_custom_field_2
• contract_parties_field_container_contract_type_custom_field_3
• contract_parties_field_container_contract_type_custom_field_4
• contract_parties_field_container_contract_type_custom_field_5
• contract_parties_field_container_contract_type_custom_field_6
• contract_parties_field_container_contract_type_custom_field_7
• contract_parties_field_container_contract_type_custom_field_8
• contract_parties_field_container_contract_type_custom_field_9
• contract_parties_field_container_contract_type_custom_field_10
• contract_price_and_payment_id
• contract_price_and_payment_created_at
• contract_price_and_payment_updated_at
• contract_price_and_payment_custom_fields …