Fivetran Release Notes

We have updated the value of the log event's connector_id property. Previously, the connector_id and connector_name properties both contained the connector name. Now, connector_id contains the connector ID, while connector_name still contains the connector name.Learn more in our Logs documentation.

We have redesigned our dashboard alerts to make them easier to read.Old alert:alerts-beforeNew alert:alerts-after

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.

We now display the role field for each user in the response for the following endpoints:

• Retrieve user details
• Invite a user
• Update a user
• List all users within a group

We have changed the data type of the picture field defining the user avatar to STRING. Now, we support both image URL (for example, http://mycompany.com/avatars/john_white.png) and Base64 data URI (for example, data:image/png;base64,aHR0cDovL215Y29tcGFueS5jb20vYXZhdGFycy9qb2huX3doaXRlLnBuZw==) values for this field. See our User Management endpoint documentation.

We now support dbt 0.19.2.

We have redesigned the connector status field to make it easier to understand. A connector's status is now displayed side-by-side with information about its activities. You can also filter your connector list by status.New connector status displayLearn more in our connector status documentation.

We now display the total table count for each schema. The total table count is updated when the filter is applied.Total table count:before-filterUpdated total table count with filter applied:after-filter

We have fixed a connector bug. Previously, when we encountered a 0 value in the time (TIMESTAMP) column of the USER_MIGRATION table, the connector would break. Now, we assign a null value instead of 0.

We have expanded the current public API endpoints Create a connection and Update a connection. Now, you can create or modify the connector that will be paused after the trial period by specifying the pause_after_trial request parameter.

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 Transformations setup form. Learn more in our dbt setup guide.

We have expanded the Create a connection endpoint. Now, you can:

• set the frequency of your syncs using the sync_frequency request parameter
• set the start time of your daily syncs using the daily_sync_time request parameter if you set the sync_frequency parameter to 1440

We have redesigned the Notifications page in the Fivetran dashboard to make it easier for you to manage your email notifications. You can now manage your notifications at the connector, transformation, and account levels to ensure that you only receive the notifications that you want. redesigned-notifications-tabLearn more about notifications in our notifications documentation.

We have added a user filter on the Users tab of the Account page. See Account Management.User Filter:user-filter

We replaced the Include new schemas and tables by default checkbox on the Schema tab of the connector details page with the Schema Change Settings menu.Schema change settings menu: schema-settings

We now support filtering by selected tables. To view only selected tables, click the filter icon, then select Only show selected tables.Selected table filter: before-filter-applyingFiltered list: after-filter-applying

We now retry new SSH Tunnel connections if we run into temporary network errors. Previously, our connection attempts failed when we ran into temporary network errors. We will roll this change out gradually over the next month.

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.

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.

We have expanded the public API endpoints Create a connection and Update a connection. Now you can authorize the Asana connection by adding the auth section to payloads.