September 2018

One Minute Sync Frequencies

Fivetran can now sync as frequently as every minute. Note that syncing every minute will only be possible if both the data source and destination can operate that quickly. Reach out to Fivetran Support if you would like this enabled for one or more of your connectors.

Warning creation and logging

We have limited the rate of user warnings to 100 per minute. File upload connectors now behave more reasonably while recording file skip issues in user facing logs. After 50 skipped file warnings, we will stop logging further file skips.

New connectors

Apache Kafka

Apache Kafka is an open-source distributed streaming platform.

Read our Apache Kafka connector documentation.

Schema changes

AdRoll

AdRoll has deprecated the ByEID field, so we no longer sync them as part of the ALL_ADVERTISABLES report.

HubSpot

We have added a new column, transcription_id, to the ENGAGEMENT_CALL table.

The HubSpot connector can now sync ecommerce data for your Sales Hub, including products and line items. We have added the following tables to support this feature:

• PRODUCT
• PRODUCT_PROPERTY_HISTORY
• LINE_ITEM
• LINE_ITEM_PROPERTY_HISTORY

Marin Software

We have renamed the following tables:

Microsoft Advertising

We have added two new tables, PRODUCT_DIMENSION_PERFORMANCE_REPORT and PRODUCT_DIMENSION_IMPRESSION_PERFORMANCE_REPORT.

Sailthru

Fivetran now sets the _fivetran_deleted column value to true for deleted records in the USER and USER_LIST tables.

Shopify

We have added a new column, note, to the ORDER table.

We have added two new columns, script_version_id and price_rule_id, to the APPLIED_DISCOUNT table.

Taboola

We have added the _fivetran_id column as a primary key in the TOP_CAMPAIGN_CONTENT_REPORT table. The item column is no longer a primary key.

Zendesk Support

The ticket_id and created_at columns are now the primary keys for the TICKET_SCHEDULE table. This change accounts for cases where a ticket is repeatedly assigned to a schedule.

In cases where multiple schedule assignment events are triggered in a single ticket audit, we now only create a record in the TICKET_SCHEDULE table for the final schedule assignment event.

We now use a Zendesk-supplied list of 100+ time zone names to map times in the TICKET_SCHEDULE table to UTC.

We have added two new columns, via_source_to_name and via_source_to_address, to the TICKET_EVENTand TICKET tables.

Improvements

Azure Monitor

We now support pushing log event data into Azure Monitor.

Read our Azure Monitor documentation.

Functions

Fivetran now adds a user_agent string related to the function_connector_name value to distinguish Fivetran's function trigger from others.

Google Ads

Customer IDs will now be included in the Specific Accounts section of the Fivetran setup form.

Jira

We have improved the response caching process to speed up our historical syncs.

Microsoft Advertising

We now support the yyyy-MM-ddTHH:mm:ss time format for the last_modified_time field in the ACCOUNT table.

MongoDB

We have fixed a bug that caused BSON_INT_32 data types to not sync during our initial syncs.

MySQL

The MySQL connector is now able to handle unescaped control characters in textual data as if they had been properly escaped.

MySQL destination

The MySQL destination now uses the load data infile strategy to write data. It requires the load_infile system variable to be set to on. For additional details, refer to our MySQL destination documentation.

Salesforce

System columns, like IsDeleted and SystemModstamp, can no longer be excluded in column configuration.

Salesforce Marketing Cloud

The Salesforce Marketing Cloud connector now supports the SentEvent endpoint.

SFTP

The No Such File Warning message is now fixed on your Fivetran dashboard.

Shopify

Users now receive warnings about GDPR data deletion requests.

Snowplow

We have added support for UA Parser Enrichment.