Release Notes

September 2024

We now support the ClickHouse destination for scheduled in code and scheduled in Fivetran transformations by default for all supported dbt Core versions.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

August 2024

We now support dbt Core* version 1.8.4. You can use this version to run your projects.

NOTE: For this dbt Core version, we don't support MySQL and SQL Server destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

July 2024

We've replaced the "Add transformation" drop-down menu with a dedicated page where you can select the type of the transformation you are adding.

June 2024

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.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Databricks on Azure destinations with OAuth authentication don't support Transformations for dbt Core* and Quickstart models.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We now disable the dbt job retry mechanism for scheduled in code and scheduled in Fivetran transformations by default.

You can change this for scheduled in code transformations by setting the value of the retryOnFailure parameter to true in the job configuration:

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

May 2024

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.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

You can now use bulk actions for Transformations, which allow you 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 the dbt job retry mechanism for scheduled in code transformations. By default, a failed job is retried 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

March 2024

We now support dbt Core version 1.7.9. 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. For dbt Core versions later than 1.4.9, we don't support SQL Server and Azure Synapse destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

Transformations and connections managed by Transformation Scheduling may be automatically retried if they fail. Since connection syncs and transformation jobs depend on each other, the rules and conditions of their retries are complex and may change in the future. We may decide to not restart connections or transformation jobs if they have failed or if their restart attempts would cause significant delays to other scheduled jobs. We may restart both connection syncs and transformation jobs up to 4 times within their scheduled sync or run interval. For connector syncs, we follow the rules described in our Sync Overview documentation whenever possible. We restart transformation jobs 5 minutes after their failure. We are gradually rolling out this feature over the next few weeks.

We now support SQL Server and Azure Synapse destinations for dbt Core* versions 1.7.3 and 1.7.9. You can use these versions to run your projects targeting those destinations.

NOTE: For dbt Core versions later than 1.1.5, we don't support MySQL destinations. For dbt Core versions later than 1.4.9 but older than 1.7.3, we don't support SQL Server and Azure Synapse destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

February 2024

We have removed the data lineage graph feature. As a result of this, we have made the following changes:

Removed the Data lineage graph tab from the transformation details page
Added the Run log tab

If you want to continue using the data lineage graph feature, contact Fivetran support.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

December 2023

We now support the following dbt Core versions:

1.1.5
1.2.6
1.5.9
1.6.9
1.7.3.

You can use these versions to run your projects.

NOTE: For dbt Core versions later than 1.1.5, we don't support MySQL destinations. For dbt Core versions later than 1.4.9, we don't support SQL Server and Azure Synapse destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We now log running transformations in real time.

real-time-logs

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We made the following UI changes to Transformations for dbt Core* scheduling:

removed the Independent scheduling type for transformations for dbt Core*.
renamed the Partially-Integrated scheduling type to Custom.
renamed the Fully-Integrated scheduling type to Integrated.

By default, we are migrating connectors using Independent schedule to Partially-Integrated.

When you select the Custom, if you have upstream connectors, we wait for the upstream connectors to complete the sync before we run the transformation by your schedule. If you don't have upstream connectors, the transformation runs by the schedule.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

November 2023

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

NOTE: For the above-mentioned versions of dbt Core, we don't support MySQL destinations. These destinations are not currently supported by a custom dbt Core adapter.

Also, we now support Azure Synapse destinations for 1.4.* versions of dbt Core.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

If your parent and child dbt models are configured to run on different schedules, the child model now runs without the parent model (dbt run --models +child --exclude parent). Previously, we included parent models in all child model runs.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We no longer support dbt Core versions below 1.0.0. You cannot select those versions anymore when configuring the dbt project.

NOTE: If you are using dbt versions below 1.0.0. in your projects, you will be automatically migrated to dbt version 1.4.9. We will communicate the exact date of the migration by email. Migration to dbt version 1.4.9 might impact the execution of dbt transformations.

We have deprecated the following versions of dbt Core:

0.18.0
0.18.1
0.18.2
0.19.0
0.19.1
0.19.2
0.20.0
0.20.1
0.20.2
0.21.0
0.21.1

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

October 2023

We now support dbt Core version 1.5.8 and 1.6.6. You can use these versions to run your projects.

NOTE: For the above-mentioned versions of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We now support access to private Git dbt Core packages in the repository with the dbt project for Scheduled in Code transformations using the same SSH key. For more information on the configuration syntax, see dbt's documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

September 2023

We now support dbt Core version 1.6.3. You can use this version to run your projects.

NOTE: For this version of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.

We now support MySQL or MariaDB destinations for dbt Core versions 1.1.*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

In order to make dbt run logs easy to read, we have updated the font and added color coding for certain statuses.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

August 2023

We now support dbt Core version 1.5.6, 1.6.0, and 1.6.1. You can use these versions to run your projects.

NOTE: For the above-mentioned versions of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL destinations. These destinations are not currently supported by custom dbt Core adapters.

Also, we now support SQL Server destination for 1.4.5 version of dbt Core.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

June 2023

We now support version 1.5.1 of dbt Core. You can use this version to run your projects.

NOTE: For this version of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL. These destinations aren't currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

March 2023

We have deprecated support for dbt Core* 1.4.1 due to a known bug. You can still run existing projects using dbt Core 1.4.1 until we implement the support for newer versions.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We now support version 1.4.5 of dbt Core. You can use this version to run your projects.

NOTE: For this version of dbt Core, we don't support SQL Server, Azure Synapse, and MySQL. These destinations aren't currently supported by custom dbt Core adapters.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

February 2023

We now support dbt Core 1.4.1. You can use this version to run your projects.

NOTE: For transformations for dbt Core*, we don't support SQL Server, Azure Synapse, and MySQL as destinations.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

January 2023

We now support dbt Core 1.0.9, 1.1.3, 1.2.4 and 1.3.2. You can use these versions to run your projects.

December 2022

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

We now support Transformations for dbt Core for the following destinations:

You can now run your dbt projects in these destinations. Learn more in our Supported destinations documentation.

November 2022

We now support environment variables for Transformations for dbt Core users. You can use environment variables to access private packages, as shown in dbt's Git Token Method documentation.

Learn how to add environment variables in our Scheduled in Fivetran setup guide or Scheduled in Code setup guide.

We now sync dbt transformations' user-facing logs into the LOG table.

You can now manually run, pause, resume, and cancel your dbt models and tests.

October 2022

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

September 2022

We now support dbt Core 1.2.1. You can use this version to run your projects.

August 2022

We have released custom scheduling for Transformations for dbt Core*. Transformations with a custom schedule run according to the schedule you choose, except when it overlaps with the upstream connector's schedule. In that case, we wait until the connector finishes syncing to run the transformation. With custom scheduling, you can:

Save on warehouse costs by running your transformation less frequently than your connector.
Ensure that all upstream connectors have synced when you run your transformation by matching its schedule to your slowest upstream connector.

Learn more in our custom scheduling documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

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

We have merged the integrated scheduling and data lineage graph experiences in Transformations for dbt Core, as well as added self-service onboarding. You can now immediately view your unified pipeline and access your integrated schedules. Previously, you had to request that these features be added to your account.

How we implement this change varies based on whether you use Transformations for dbt Core today:

If you're a current Transformations for dbt Core user, we provide an optional upgrade path that automatically creates new integrated transformations from your connected dbt project.
If you're not a current Transformations for dbt Core user, once you connect your dbt project to Fivetran, we enable integrated scheduling and data lineage graphs by default.

Learn more in our integrated scheduling and data lineage graph documentation.

June 2022

We have restored the manual sync functionality for your connectors if you have Transformations for dbt Core enabled. When you click the Sync now button in the dashboard, the sync runs. Once the sync is completed, we run all dependent models.

We now support dbt Core 1.0.7, 1.0.8, and 1.1.1. You can use these version to run your projects.

May 2022

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.

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

April 2022

We now support dbt Core 1.0.5. You can use this version to run your projects.

March 2022

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

February 2022

We have released integrated scheduling for Transformations for dbt Core*. Integrated scheduling lets you automatically trigger dbt model runs immediately after a connector sync completes. As a result, it reduces data latency by running transformations on new data as soon as it's loaded into your destination. It also helps you save on cloud computing costs by not running transformations on outdated data. To learn more about integrated scheduling, see Transformations for dbt Core.

Learn how to add your dbt models and schedule their runs directly in the Fivetran dashboard.

Add new transformation for dbt Core in Fivetran dashboard

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

You can now specify your dbt version in the Transformations for dbt Core setup form. Previously, we required you to use the deployment.yml file to specify your dbt version. If you included a dbt version in the deployment.yml file, we now ignore it. To learn more, see the Transformations for dbt Core setup guide.

January 2022

We now support dbt 1.0.0 and 1.0.1. You can use these versions to run your projects.

December 2021

We now support dbt 0.21.1. You can use this version to run your projects.

Now, you can specify the target name in the dbt project setup form. The specified value overrides the target name value present in deployment.yml.

Fivetran has created a dbt Core*-compatible social media reporting model that aggregates data from our most popular social media connectors into a unified table. This pre-built model allows you to compare how your posts perform on each social media platform.

The social media reporting model supports the following connectors:

Facebook Pages
Instagram Business
LinkedIn Company Pages
Twitter Organic

You do not need to have all four social media connectors to use this model, though you should have at least two.

Learn more in our social media reporting model documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

November 2021

We now support dbt 0.21.0. You can use this version to run your projects. You can upgrade your existing projects by following dbt's migration guide.

October 2021

dbt commands may produce output too large to be sent to external logging systems as a part of dbt_run_succeeded and dbt_run_failed log events. Now, we truncate dbt output for those log events if it exceeds 200 lines. To get the complete log, go to the Transformations page in your Fivetran dashboard and select the transformation you want to check. Then, select the particular run and view the Run Details.

September 2021

We now support dbt 0.20.2. You can use this version to run your projects.

August 2021

We now support dbt 0.20.1. You can use this version to run your projects.

We now support up to 32 dbt threads. Note that the number of threads must be compatible with your destination type. For example, Snowflake supports only 8 concurrent queries.

July 2021

We now support dbt 0.19.2.

We now support dbt 0.20.0. You can use this version to run your projects. You can upgrade your existing projects by following dbt's migration guide.

June 2021

We now skip the dbt docs serve command, which starts a webserver on port 8000 to serve documentation locally. This command is not intended to be used with Fivetran.

You can now customize the credentials that Fivetran uses to access your Snowflake destination to run dbt jobs. Add your credentials in the Credentials section of your dbt Tranformations setup form. Learn more in our dbt setup guide.

May 2021

We now support dbt 0.18.2 and 0.19.1.

March 2021

Fivetran has created a dbt Core*-compatible ad reporting model that aggregates data from our most popular advertising connectors into a unified table. This pre-built model allows you to compare how your ad spend converts into clicks and impressions on each advertising platform.

The ad reporting model supports the following connectors:

Facebook Ads
Google Ads
LinkedIn Ad Analytics
Microsoft Ads
Pinterest Ads
Twitter Ads

You do not need to have all six advertising connectors to use this model, though you should have at least two.

Learn more in our ad reporting model documentation.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

We now support dbt 0.19.0. You can use this version to run your projects. You can upgrade your existing projects by following dbt's migration guide.

We've increased the maximum number of threads that can be used by dbt jobs from 4 to 8.

We no longer support dbt 0.17.2.

You can now customize the name of the dbt target that your dbt jobs use. Add the dbt target in the optional targetName field in the deployment.yml file. Learn more about the deployment.yml file in our dbt setup guide.

February 2021

We added setup tests in the dbt Transformations setup form. When you click Save & Test, Fivetran checks the credentials and connection to your repository.

Previously, Firetran synced projects immediately after you clicked Save & Test. Now Fivetran syncs your project within a few minutes after the setup tests succeed.

January 2021

You can now enable email notifications for each of your dbt transformations on your Fivetran dashboard's Notifications tab. To learn more about email notifications, see our Notifications documentation.

December 2020

Fivetran now supports flushing dbt transformations event data to supported log services.

Each log service has a unique path for this data:

Log Service	Path Pattern
AWS CloudWatch	`{ACCOUNT_NAME}/{GROUP_NAME}/dbt/{DBT_JOB_NAME}`
Azure Monitor	`{ACCOUNT_NAME}_{GROUP_NAME}_dbt_{DBT_JOB_NAME}_CL`
Google Cloud Logging	`{ACCOUNT_NAME}-{GROUP_NAME}-dbt-{DBT_JOB_NAME}`
Splunk Logging	`channel.account="{ACCOUNT_NAME}"` `channel.group="{GROUP_NAME}"` `channel.service="dbt"` `channel.schema="{DBT_JOB_NAME}"`

Learn more in our Logs documentation.

You can now choose the version of dbt that will run your projects. You can specify it in the deployment.yml file.

We support 3 versions of dbt:

0.17.2
0.18.0
0.18.1

If you don't specify dbt version in deployment.yml file, we'll use the version 0.18.0 to run your projects.

Now dbt Transformations support the Databricks destination. If you use Databricks as a destination, you can just set up your dbt Transformations using our guide; no additional steps are required.