Fivetran Release Notes

We now validate the Function App name more strictly for Azure Functions connections. In line with Microsoft's Azure naming rules, the name must be 2-64 characters long, can contain only letters, digits, and hyphens, and can't start or end with a hyphen. If your Function App name includes Azure-generated, dot-separated parts (for example, <app-name>.<region>-01), those parts can contain only letters, digits, hyphens, and dots. This ensures Fivetran sends requests only to your Function App's azurewebsites.net address.If your connection uses a name that doesn't follow these rules, the connection test or sync fails with an invalid input error. To fix it, enter only the Function App name exactly as it appears in the Azure portal, without https://, paths, ports, or query strings, in the Function App field of the connection setup form. For more information, see our setup instructions.

We have added support for dbt version 1.12.5 for the following destinations:

• BigQuery
• Databricks
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Azure Synapse
• Teradata Vantage

{% note %}Although other destinations support different dbt versions, they don't support dbt 1.12.5 due to lack of available dbt adapters for this version.{% /note %}We have added support for dbt version 2.0.6 for the following destinations:

• BigQuery
• Databricks
• Redshift
• Snowflake

{% note %}Although other destinations support different dbt versions, they don't support dbt 2.0.6 due to lack of available dbt adapters for this version.{% /note %}

We have identified and fixed a potential issue with delete capture for some application connectors, particularly for records in child tables. If your connection was affected by the previous behavior, we will re-sync the affected tables on October 3, 2026 to ensure data accuracy. We will not re-sync connections that were not affected.The re-sync will not contribute to your Monthly Active Rows (MAR).Expand to see the list of affected connectors and tables

Connector

Tables

AccuLynx

FINANCIAL, FINANCIAL_AMENDMENT, FINANCIAL_WORKSHEET, INVOICE, INVOICE_SECTION, INVOICE_SECTION_ITEM, JOB, JOB_CONTACT, JOB_CONTACT_EMAIL_ADDRESS, JOB_CONTACT_PHONE_NUMBER, JOB_TRADE_TYPE, LEAD_HISTORY, and MILESTONE_HISTORY

Appcues

EVENT, EVENT_TEMP, and USER_PROFILE

BigCommerce

CHANNEL, CHANNEL_ACTIVE_THEME, CHANNEL_APP, CHANNEL_LISTING, CHANNEL_VARIANT, CUSTOMER, CUSTOMER_ADDRESS, CUSTOMER_ADDRESS_FORM_FIELD, CUSTOMER_ALLOW_CONSENT, CUSTOMER_ATTRIBUTE_VALUE, CUSTOMER_CHANNEL, CUSTOMER_CONSENT, CUSTOMER_DENY_CONSENT, CUSTOMER_FORM_FIELD, CUSTOMER_SETTING_PER_CHANNEL, CUSTOMER_STORE_CREDIT, ORDER_BILLING_ADDRESS_FORM_FIELD, ORDER_COUPON, ORDER_MESSAGE, ORDER_METAFIELD, ORDER_PAYMENT_METHOD, ORDER_PRODUCT, ORDER_PRODUCT_DISCOUNT, ORDER_PRODUCT_OPTION, ORDER_REFUND, ORDER_REFUND_ITEM, ORDER_REFUND_PAYMENT, ORDER_SHIPMENT, ORDER_SHIPMENT_ITEM, `ORDER_SHIPPING_A…

We have added the following new tables:

• INVENTORY_PAR_LOCATION
• INVENTORY_PAR_LOCATION_DOCUMENT_STATUS
• INVENTORY_PAR_LOCATION_LINE
• INVENTORY_PAR_LOCATION_LINE_BIN
• INVENTORY_PAR_LOCATION_LINE_BIN_REFERENCE
• INVENTORY_PAR_LOCATION_LINE_SPLIT
• INVENTORY_PAR_LOCATION_LINE_SPLIT_WORKTAG
• INVENTORY_PAR_LOCATION_LINE_WORKTAG
• INVENTORY_PAR_LOCATION_WORKTAG

We have added the following new tables:

• GIFT_HIERARCHY
• GIFT_HIERARCHY_CHILDREN
• GIFT_HIERARCHY_GIFT

We have added two new tables, GRANT_HIERARCHY and GRANT_HIERARCHY_INCLUDED_GRANT.We have added the following new tables:

• GIFT
• GIFT_ADJUSTMENT_WORKTAG
• GIFT_ALLOWED_WORKTAG
• GIFT_INCOME_DISTRIBUTION_AMOUNT_RULE
• GIFT_INCOME_DISTRIBUTION_AMOUNT_RULE_WORKTAG
• GIFT_INCOME_DISTRIBUTION_PERCENT_RULE
• GIFT_INCOME_DISTRIBUTION_PERCENT_RULE_WORKTAG
• GIFT_PURPOSE
• GIFT_PURCHASE_WORKTAG
• GIFT_REINVESTMENT_WORKTAG
• GIFT_RELATED_WORKTAG
• GIFT_RESPONSIBLE_ORGANIZATION
• GIFT_RESTRICTION
• GIFT_RESTRICTION_PURPOSE

We have added three new tables, GRANTS, GRANT_ALLOWED_WORKTAG, GRANT_HIERARCHY_REFERENCE and GRANT_RELATED_WORKTAG.

We have added a new NetWeaver Connection mode to the connector. This mode connects Fivetran to your SAP system through the SAP NetWeaver Application Server using RFC calls, instead of connecting directly to the Oracle database that backs your SAP system. We still read your Oracle redo and archive logs for incremental updates, but relay file access through your SAP Application Server using new RFC-enabled functions in the Fivetran NetWeaver API.To use this mode, select NetWeaver Connection in the connection setup form and provide your SAP Application Server host, system number (SYSNR), client number (CLIENT), username, and password. You also need to install the Fivetran NetWeaver API on your SAP system. Oracle Database Connection remains the default connection mode.To use this mode, download and install Fivetran NetWeaver API v1900334 or later.For more information, see our Connection modes and SAP ECC on Oracle Setup Guide documentation.