Customer triggered table re-syncs
You can now trigger re-syncs of individual tables from your Fivetran dashboard:
The re-sync button appears when you hover your cursor over the row that contains the table name.
This feature is available for the following connectors:
- Netsuite SuiteAnalytics
- SQL Server
Google Analytics 360
Google Analytics 360 provides the tools and support that enterprise teams need to get actionable insights from their data.
Lever is a modern recruiting software that streamlines the hiring process and simplifies the applicant tracking system.
ServiceNow is a cloud platform that provides service management software as a service.
brand field can have a
null value in the Bing Ads API response, it is no longer the primary key in the following tables:
This change affects version 1 and version 2 of the Bing Ads API.
Facebook Ad Account
We have removed the
FAILED_DELIVERY_CHECKS table from the Facebook Ad Account connector due to data retrieval problems and lack of analytical utility.
We have replaced the
locale_name field with
locale in the following tables:
Salesforce Marketing Cloud
We have added a new field,
version, to the
We have removed the suffix
_HISTORY from all table names.
We have designated
_fivetran_id as the only primary key in all
REPORT tables to account for null values in other fields.
We have dropped the
deleted column from the
You can now have a space in your log group name without causing problems in your Fivetran dashboard.
We have released version 2 of the Bing Ads connector, which allows you to fetch
JOBtable now includes the field
SCHEDULED_INTERVIEWtable now includes the fields
We have increased the Help Scout API rate limit, allowing us to easily retry our API connections when failures occur.
We have released a new version of the Intercom connector, now with an improved schema. You can find additional information in our Intercom documentation.
Thanks to leveraging Intercom webhooks, we now support the
delete function in the following tables:
We have added support for OAuth, as Jira is deprecating basic authentication with password.
We have identified and fixed an extremely rare bug that can cause data to be missed during binary log replication. The bug meant that, in some cases, our system believed that all data had been successfully synced, when the binary log replication process had actually stopped prematurely.
We have fixed the incremental update of subtables. All subtables of subtables will also be updated recursively. For example, if the
TRANSACTIONS table is updated, then its subtable
TRANSACTION_LINES will be updated, along with
TRANSACTION_LINES's own subtables
The ServiceNow connector can now sync tables which do not have
We have improved the Taboola connector's capacity to support very large data files.
TLS Certificate Verification Changes
You are no longer able to configure self-signed certificates for destination connectors. We plan to release new UI tools in the coming weeks to empower security teams to register and pin certificate authorities with Fivetran.
We have added GZIP support for Webhook API requests.