May 2022

Account Migration to New RBAC Model

We migrated all existing accounts to our new role-based access control (RBAC) model. See our Role-Based Access Control documentation to learn about the benefits of the new RBAC model and to find out the closest equivalents between the roles in the new and deprecated RBAC model.

Dashboard Improvements

Reduce or pause syncs for broken connectors

We now reduce a connector's sync frequency to 24 hours when its syncs have failed for over 14 days due to an unresolved Task.

If the connector's syncs are still failing, we pause it for an additional 14 days (for a total of 28 days after the first sync failure).

Fivetran AWS India Servers

We have added new servers in the AWS Asia Pacific (Mumbai) region.

If you're on a Business Critical plan, you can now select this region in your destination setup form. Connectors configured in a destination run in their designated cloud and region, meaning that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in India, your data does not leave India during processing.

If you're on an Enterprise or Business Critical plan, this is the default region if you choose India as your data processing location and AWS as your cloud provider.

We now support AWS Private Link connections to sources and destinations in ap-south-1 region.

For more information, see our data residency documentation.

Transformations for dbt Core

Data lineage graphs

We have added data lineage graphs (DLGs) for Transformations for dbt Core - Scheduled in Fivetran users. DLGs visualize the flow of data from your connectors to your destination. You can also use them to troubleshoot failed transformation runs.

Learn more in our data lineage graph documentation.

dbt Core versions 1.0.6 and 1.1.0 support

We now support dbt Core 1.0.6 and 1.1.0. You can use these versions to run your projects.

New connectors

Microsoft Lists

Microsoft Lists is a Microsoft 365 application for work management and tracking.

Read our Microsoft Lists connector documentation.

SharePoint

SharePoint is a file storage and collaboration service.

Read our SharePoint connector documentation.

Schema changes

AWS Inventory

We now sync the following Route 53 data types:

• HostedZone
• ResourceRecordSet

We are gradually rolling out this feature to all existing connectors.

NOTE: You need to add the "route53:ListHostedZones" and "route53:ListResourceRecordSets" permissions in the Create IAM policy step of the AWS Inventory setup guide to be able to sync the Route 53 data types.

Delighted

We have added a new table, RESPONSE_TAG, to replace the PERSON_TAG table. We now sync the API response tag data to the RESPONSE_TAG table. We will deprecate the PERSON_TAG table after August 2, 2022. Be sure to update your queries.

Iterable

We have renamed the unique_emails_opens column to unique_email_opens because Iterable renamed the metric. This change affects the CAMPAIGN_METRICS and EXPERIMENT_METRICS tables. For more information, see Iterable's Unique Email Opens metric release note. We now sync new data into the new unique_email_opens column in the destination tables. Contact our support team if you want to backfill older data in the column. You may experience slow sync speeds when you backfill the older data into the column.

We now sync smsClick events into the EVENT table.

Jira

We now sync the Affected Services, Customer Request Type, and Approvals fields with a customer request from Jira Service Management (formerly Jira Service Desk). We sync the Affected Services, Customer Request Type, and Approvals fields into the following tables:

• APPROVAL
• APPROVER
• REQUEST
• REQUEST_TYPE
• SERVICE

See the Jira ERD for more information.

We are gradually rolling out this feature to all existing connectors. When it's available for your connector, you will see the tables above on the Schema tab. To fetch data for all issues, re-sync your connector.

NOTE: Previously, we only synced the name subfield in the Customer Request Type field. We kept this logic for compatibility. See the January 2021 Release Notes for more information.

Square

We have changed the composite key of the ORDER_LINE_ITEM_MODIFIER table. The new composite key is a combination of the uid and order_line_item_id columns. Be sure to update your queries.

Twitter Ads

We have changed the segmentation of the line_item_cities_report report.

We have renamed the country_name column to location_name.

We have added a new column, location_type.

YouTube Analytics

We now sync the subtitle_language_autotranslated field of the channel_subtitles_a2 report.

Improvements

Airtable

Our Airtable connector now uses the Airtable Webhooks API. New connectors created after May 13, 2022, will utilize the Webhooks API to read your data. We are gradually migrating the existing connectors to the new API. If you'd like to use this improvement immediately, contact our support team.

HubSpot

The HubSpot connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. HubSpot's priority-first syncs fetch the most recent 24 hours' worth of data from the EMAIL_EVENT table and its child tables. To learn more, see our priority-first sync documentation.

Now, the EMAIL_EVENT table syncs data for only the event types you define in the source EMAIL_EVENT_* child tables. For more information, see our documentation.

Iterable

You can now select and deselect tables to be synced on the Schema tab of the Connector Details page in your Fivetran dashboard.

Kantata

We now re-sync the WORKSPACE table once a day to detect deleted records.

Klaviyo

You can now select and deselect tables to be synced on the Schema tab of the Connector Details page in your Fivetran dashboard.

Mailchimp

We have optimized the connector to minimize the 503 service unavailable error. This change automatically triggered a full re-sync of the CAMPAIGN_RECIPIENTS table for some campaigns. This re-sync is a one-time occurrence.

MongoDB

We now automatically reschedule the connector's sync when oplog or change stream cursors expire. For more information about cursor expiry, see our documentation.

ServiceNow

Now, we use false as the initial value for the _fivetran_deleted column. Previously, we used null as the initial value. We are gradually rolling out this improvement to all our existing connectors.

NOTE: This change only applies to connectors for which the Capture Deletes feature is enabled. See our ServiceNow documentation for details.

Zendesk Sell

Our Zendesk Sell connector is now generally available. Read our Zendesk sell connector documentation.

REST API Improvements

New and Updated REST API Endpoints

We have implemented a new API endpoint for our REST API, Re-sync Connector Data (Historical Sync), that allows you to trigger a full historical sync of a connector or multiple schema tables within a connector.

We have updated the Sync Connector Data endpoint with a new path, sync. We also added a new payload parameter, force, that allows you to force a sync, even if a sync is already in progress.