Fivetran Release Notes

We have changed the sync strategy for the EVENT_REPORT table. We no longer re-import the EVENT_REPORT table to capture updates and deletes.

We no longer capture deletes for CONVERSATION table.

We have removed the weekly re-import for the INCIDENT and INCIDENT_METRIC_BUCKET tables.

We sunset our Verizon Media connector. Effective June 1, 2024, we will no longer support the creation of new Verizon Media connections.

For scheduled in Fivetran transformations for dbt Core, we have added a new option, Smart syncing, to the Custom Scheduling group of the Schedule tab.

• With the Smart syncing option enabled, the models run on the set schedule. However, when their run schedule overlaps with the sync schedule of their upstream connectors, models wait until connectors have finished syncing before running.
• With the Smart syncing option disabled, the models run on the set schedule regardless of the upstream connectors' sync schedule and state.

We no longer re-import the following tables and their child tables to capture deletes:

• CONVERSATION
• EMAIL_SERIES_CAMPAIGN
• EMAIL_SERIES_SUBSCRIBER_ACTIVE
• EMAIL_SERIES_SUBSCRIBER_REMOVED
• EMAIL_SERIES_SUBSCRIBER_UNSUBSCRIBED
• PEOPLE
• SINGLE_EMAIL_CAMPAIGN
• WORKFLOW

We now support the dbt job retry mechanism for scheduled in code transformations. By default, we retry a failed job for up to 4 times.You can change this by setting the value of the retryOnFailure parameter to false in the job configuration:

- name: daily
  schedule: 0 12 * * *
  retryOnFailure: false

We no longer capture deletes for the following tables:

• BILLING_ATTEMPT
• ORDER_LINE_ITEM
• PRODUCT
• SUBSCRIBER
• SUBSCRIPTION_ACTIVITY

We have renamed our DEAR connector to Cin7 Core. This name change applies to the Fivetran dashboard and our documentation.

We have added two new tables, EPIC_STORY_CUSTOM_FIELD and STORY_CUSTOM_FIELD.We have added a new column, group_id, to the STORY table.

You can now use bulk actions for Transformations, to perform any of the following actions on multiple transformations at once:

• Pause selected transformations
• Resume selected transformations
• Edit schedule of selected transformations
• Remove selected transformations

We now support dbt Core version 1.7.14. You can use this version to run your projects.{% note %}For dbt Core versions later than 1.1.5, we don't support MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.{% /note %}

Our Connection Management API now supports a new endpoint, Create a Connection Schema Config. The endpoint allows you to configure the schema before the initial sync without reloading it.

We have made the following updates to our Care Quality Commission connector to support the changes in the Care Quality Commission API:

• In the connector setup form, we replaced the Partner code field with the Primary key field. For more information, see our setup instructions.
• In the API config parameters, we replaced the partner_code parameter with the primary_key parameter. For more information, see our REST API documentation.

We no longer generate the following log events:

• STATUS (deprecated)
• DISCONNECT_BI_TOOL
• CONNECT_BI_TOOL
• UPDATE_BI_TOOL
• CREATE_STAGING_TABLE
• APPLY_TIER_LIMITATION
• MIGRATE_SCHEMA_CONFIG
• SCHEMA_MIGRATION_FAILURE
• SCHEMA_MIGRATION_SUCCESS
• DISMISS_WARNING
• TRANSFORMATION_RUN_START
• TRANSFORMATION_RUN_SUCCEEDED
• TRANSFORMATION_RUN_FAILED

For more information, see our Logs documentation.

We now incrementally sync the LOGS table and its child tables to capture new records.

We have changed the sync strategy for our dbt Cloud connector. We now incrementally sync the RUN table and its child tables to capture new records. However, we will continue to re-import the remaining tables.