Fivetran Release Notes

We have implemented offset-based pagination for the SEGMENT endpoint to improve data management.

We added a new design for Connector List Filter on Connector Page.Connector List

The Azure Cosmos DB for NoSQL connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

We now capture deletes for the CONVERSATION_ACTION_HISTORY_REPORT table.

We have changed our sync strategy and now incrementally sync the CONVERSATION and CUSTOMER tables.

You can now add multi-connector Quickstart transformations for the following data model types:

• Ad reporting
• Social media reporting
• Shopify holistic data model

1. Select the relevant package provided the supported connectors have already been created. Select package
2. Select the relevant connectors from the list of available connectors. Add\_package
3. Select the schedule: Integrated or Custom. Integrated schedule Custom schedule
4. Click Save. The transformation will be created and run by the dbt-runner.

Azure Synapse destinations now support the Hybrid Deployment model. We are gradually rolling out this feature to all existing destinations. For more information, see our setup guide.

The Ometria 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. Ometria's priority-first syncs fetch the most recent seven days' worth of data from the ORDERS, PROFILE, and UNSUBSCRIBED_CONTACTtables.To learn more, see our priority-first sync documentation.

We have implemented a new Destination Management API endpoint for our REST API. You can now leverage the new List all destinations within an account feature.

We added a new design for the Connector List on the Connector Page.Connector List

We now support priority-first sync for the CHURN_SCORE_CALCULATION and CHURN_SCORE_FACTOR_CALCULATION tables.We now sync only the last 2 days' worth of data for the CHURN_SCORE_CALCULATION table during each incremental sync.

We can now retrieve and sync your archived issues into the ISSUE table.

We now incrementally sync the EVENT table.

We added a new tab where you can add, view, and rotate the previously introduced System Keys in your Fivetran dashboard. To manage System Keys, you must have administrative permissions on the account. Learn more in our System Keys management documentation.system\_keys\_listYou can add a new System Key by uploading a JSON file with the key access rules. We then validate the file and show a summary of key permissions.add\_system\_key

We have changed our sync strategy and now re-import the COLLECTION table weekly to capture updates and deletes.

We no longer capture deletes for the CANDIDATE table and its child tables.

We have removed the Password drop-down menu from the connection setup form.

We now restrict API users from triggering syncs if:

• the append_file_option field is set to the upsert_file_with_primary_keys value
• primary keys are not defined in the schema configuration

We also restrict the following actions:

• Creating a new connection in an un-paused state via API
• Updating the connection's paused field to false via API request
• Forcing the connection sync or re-sync via API request

We have renamed our Local Processing Agent Management API to Hybrid Deployment Agent Management API. We will stop supporting the previous paths that were applicable to the Local Processing Agent Management API in 3 months from now. You must migrate to the new API before we stop supporting the old paths.We have added a new parameter, hybrid_deployment_agent_id, to the Connector Management API and Destination Management API. The new parameter defines the Hybrid Deployment Agent ID and is a duplicate of the local_processing_agent_id parameter. We will remove the local_processing_agent_id parameter in future.