Fivetran Release Notes

In addition to being able to change the default target, you can now define multiple additional targets when setting up a transformation for dbt Core.dbt setup form\_multiple\_targetsDeleting a custom target deletes the models associated with it.delete\_target\_modalWhen you set up a transformation, you assign one of the targets you defined for your dbt project to be used with the model. You can set up several transformations using the same model but different targets.transformation\_addTransformations that use additional targets have a pill displaying the name of the additional target used.transformations\_list

We have removed the USER_SESSION and USER_EVENT tables and added two new tables, SEGMENT and SEGMENT_EVENT, to sync the user session and user event data in these tables.

We have changed the primary key of the PARTNER_OVERLAP_COUNT table. The new primary key is the _fivetran_id column. Previously, the primary key was a combination of the index and partner_organization_id columns.

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.

Our AWS MSK destination is now generally available. Read our AWS MSK destination documentation.

We have updated the sync strategy for the PEOPLE table to ensure data integrity. We now use data from the date_modified column to incrementally sync the table. We also re-import the table once a week to capture deletes.

We have renamed the array column to arrays in the CATALOG_TYPE_SCHEMA_ATTRIBUTE table.We have changed the primary key of the IDENTITY_UTILITY_ROLE table. The new composite primary key is a combination of the index and identity_utility_name columns. Previously, the index column was the primary key.We have removed the IDENTITY_UTILITY table.

We have renamed the API Key field to User token in the connector setup form. We have also modified our REST API configuration parameters and replaced the api_key parameter with user_token. For more information, see our setup instructions and REST API config.

We have removed the survey_id column as a part of the composite primary key for the following tables:

• BUTTON_NEXT_RESPONSE
• DATE_RESPONSE
• DROPDOWN_RESPONSE
• EMPTY_RESPONSE
• FORM_RESPONSE
• MATRIX_RESPONSE
• MULTIPLE_RESPONSE
• NPS_RESPONSE
• RANKING_RESPONSE
• RATING_RESPONSE
• RESPONSE
• SINGLE_RESPONSE
• MILEY_SCALE_RESPONSE
• TEXT_RESPONSE

We have changed the composite primary key of the TIMESHEET_ENTRY table. The employment_id and organization_id columns are no longer part of the composite primary key for this table.

We have renamed the following columns in the tables below:

Table Name

Old Column Name

New Column Name

CALIBRATION_ANALYST_SECTION

percent

percentage

COACHING

snapshot

snapshots

WORKLOAD_ASSIGNMENT_FILTERS

group

groups

We have updated the Transformation Notifications to support model-based transformations. You can create these transformations using Quickstart packages, or by selecting models from your Git dbt projects.

We have added a new configuration option, URL format, to the connector setup form to support all regional variants of the Fountain URL. For more information, see our setup instructions and REST API config.

Our HVR Registration API resource is now in beta. You can now leverage the Register a new hub feature.

We no longer use your Integral Ad Science client ID and client secret to access and sync your data. To support this enhancement, we have made the following changes:

• Removed the Client ID and Client Secret fields from the connector setup form.
• Removed the client_id and client_secret parameters from the REST API configuration.

For more information, see our setup instructions and REST API config.

We have removed the forced_pause_connector dashboard activity log event. We now send an automated pause event, pause_connector with the actor:Fivetran attribute. We issue the automated pause event either for broken or trial expired connectors.

We now capture deletes for all tables. To support this feature, we have changed the connector's sync strategy. We now re-import all tables. Previously, we incrementally synced all the tables.

You can now configure your Buildkite connector using the Fivetran REST API. This feature is available for Free, Standard, Enterprise, and Business Critical accounts.