September 2025

Connector SDK

`fivetran-connector-sdk` PyPI package

We have released version 2.0.2 of the fivetran-connector-sdk PyPI package. This release adds the following:

Improved logging
Updated tester performance
Minor fixes and improvements

Schema changes

Adobe Workfront

Effective September 4, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to support a feature enhancement.

4 total changes • 0 possible breaking changes

Table/column	Change type	New name
`PORTFOLIO`
table	New Table	`PORTFOLIO`
`PORTFOLIO_CUSTOM_VALUE`
table	New Table	`PORTFOLIO_CUSTOM_VALUE`
`PROGRAM_CUSTOM_VALUE`
table	New Table	`PROGRAM_CUSTOM_VALUE`
`PROJECT_CUSTOM_VALUE`
table	New Table	`PROJECT_CUSTOM_VALUE`

ADP Workforce Now

We have added the following child tables to the WORKER_TIME_CARD table:

WORKER_TIME_CARD_DAY_ENTRY
WORKER_TIME_CARD_TIME_ENTRY
WORKER_TIME_CARD_LABOR_ALLOCATION
WORKER_TIME_CARD_ENTRY_TOTAL

We are gradually rolling out this change to all connections.

Appcues

Effective September 1, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to support a feature enhancement.

9 total changes • 0 possible breaking changes

Table/column	Change type	New name
`BANNER`
table	New Table	`BANNER`
`BANNER_STEP`
table	New Table	`BANNER_STEP`
`BANNER_STEP_TRAIT`
table	New Table	`BANNER_STEP_TRAIT`
`BANNER_TRAIT`
table	New Table	`BANNER_TRAIT`
`CHECKLIST`
table	New Table	`CHECKLIST`
`LAUNCH_PAD`
table	New Table	`LAUNCH_PAD`
`LAUNCH_PAD_STEP`
table	New Table	`LAUNCH_PAD_STEP`
`LAUNCH_PAD_TRAIT`
table	New Table	`LAUNCH_PAD_TRAIT`
`TAGS`
table	New Table	`TAGS`

Apple App Store

We have added a new table, SALES_WIN_BACK_ELIGIBILITY, to store the win-back offer eligibility data for churned subscription customers. We are gradually rolling out these changes to all existing connections.

Cvent

Effective September 1, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to support a feature enhancement.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`CONTACT`
column	New Column			`source_id`

Flywheel Digital

Effective September 2, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`SEARCH_TERM`
column	New Column			`weight`

Gladly

Effective September 1, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to enhance its usability.

1 total changes • 0 possible breaking changes

Table/column	Change type		Old name	New name	Notes
`AGENT_SUMMARY_GLANCE_REPORT`
table	New Table			`AGENT_SUMMARY_GLANCE_REPORT`

JustCall

Effective September 4, 2025 we use a new September 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.

We are updating the connector schema to align with source changes.

You should review the changes and update your downstream queries if necessary. Failing to do so may lead to missing or incomplete data in your data pipelines.

43 total changes • 18 possible breaking changes

Table/column	Change type	Old name	New name
`CONTACT`
column	Discontinued Column	`company`
column	Discontinued Column	`firstname`
column	Discontinued Column	`lastname`
column	Discontinued Column	`notes`
column	Discontinued Column	`phone`
column	New Column		`address`
column	New Column		`birthday`
column	New Column		`created_at`
column	New Column		`name`
column	New Column		`occupation`
column	New Column		`phone_number`
column	New Column		`status`
column	New Column		`status_updated_at`
`CONTACT_CUSTOM_FIELD`
table	New Table		`CONTACT_CUSTOM_FIELD`
`CONTACT_OTHER_PHONES`
table	Discontinued Table	`CONTACT_OTHER_PHONES`
`GROUPS`
table	New Table		`GROUPS`
`PHONE_NUMBER`
column	Discontinued Column	`agent_id`
column	Discontinued Column	`capabilities_fax`
column	Discontinued Column	`capabilities_voice`
column	Discontinued Column	`custom_name`
column	Discontinued Column	`friendly_name`
column	Discontinued Column	`phone`
column	New Column		`availability_setting`
column	New Column		`business_registration`
column	New Column		`capabilities_call`
column	New Column		`current_status`
column	New Column		`friendly_number`
column	New Column		`justcall_line_name`
column	New Column		`justcall_number`
column	New Column		`number_owner_id`
column	New Column		`number_type`
column	New Column		`sms_compliance`
`PHONE_NUMBER_TEAM_MEMBER`
table	New Table		`PHONE_NUMBER_TEAM_MEMBER`
`PHONE_NUMBER_USER_GROUP`
table	New Table		`PHONE_NUMBER_USER_GROUP`
`TEAM`
table	Discontinued Table	`TEAM`
`TEXT_TAG`
column	Discontinued Column	`agent_id`
column	Discontinued Column	`color`
column	Discontinued Column	`datetime`
column	New Column		`color_code`
column	New Column		`created_at`
column	New Column		`created_by_agent_id`
`USER_GROUP`
column	Rename Column	`id` 🔑	`group_id` 🔑
column	Discontinued Column	`name`

Sage Intacct

We have resolved a data integrity issue in the Sage Intacct connector that impacts the GLACCOUNTBALANCE table. We have updated the primary key RECORDNO calculation for this table.

Earlier, we calculated the primary key as a hash of the following columns:

accountno
accountrec
accounttitle
bookid
classdimkey
classid
classname
contractdimkey
contractid
contractname
createdby
currency
customerdimkey
customerid
customername
departmentid
employeedimkey
employeeid
employeename
endbal
forbal
gldimcompensation_type
gldimservice_line
itemdimkey
itemid
itemname
location_id
locationno
modifiedby
openbal
period
projectdimkey
projectid
projectname
recordno
record_url
taskdimkey
taskid
taskname
totadjcredit
totadjdebit
totcredit
totdebit
vendordimkey
vendorid
vendorname
whencreated

Now, we calculate the primary key as a hash of the following columns:

accountno
accountrec
bookid
classdimkey
classid
classname
contractdimkey
contractid
createdby
currency
customerdimkey
customerid
departmentid
employeedimkey
employeeid
gldimcompensation_type
gldimservice_line
itemdimkey
itemid
locationid
locationdimkey
locationno
openbal
period
projectdimkey
projectid
recordno
record_url
taskdimkey
taskid
vendordimkey
vendorid
whencreated

To correct historical data in your destination:

You can initiate a free re-sync for the GLACCOUNTBALANCE table until September 30, 2025, from Fivetran.
If you choose not to re-sync, only incremental data from September 1, 2025, will reflect the updated RECORDNO calculation.

Re-syncs will result in a large number of API calls to Sage Intacct, which may lead to additional charges at the source as per the Sage Intacct API pricing model.
GLACCOUNTBALANCE is a high-volume table, so sync times may increase during the re-sync.
You might notice an increase in MAR as we synced previously missed rows.

Slack

We have removed the following tables for connections created on or after September 3, 2025:

CHAT_PERMALINK
MESSAGE
MESSAGE_ATTACHMENT
MESSAGE_BLOCK
MESSAGE_BLOCK_ELEMENT
MESSAGE_BLOCK_FIELD
MESSAGE_FILE
MESSAGE_REPLY_USER
MESSAGE_REACTION

Workday Financial Management

We have updated the data type of the supplier_invoice_reference_number column in the SUPPLIER_CONTRACT table from BOOLEAN to STRING.

Workday HCM

We have added a new column, job_family_id, to the WORKER_POSITION_HISTORY and WORKER_POSITION tables.

Improvements

Databricks destination

You can now use a service principal to authenticate external Azure staging in Hybrid Deployment.

FTP

We now support syncing files to multiple destination tables and handling file patterns in Merge Mode. To support these features, we have made the following changes to the connection setup form:

Added the Files field and sub-fields Table name and File pattern, that enable you to define destination tables and specify the file pattern names.
Renamed the Destination table field to Table group name to enable unique identification of connections that share the same destination schema name.

For more information, see our setup instructions and REST API configuration. We are gradually rolling out these enhancements to all existing connections.

Placer.ai

We now re-import the VISIT_BY_TREND table once a week to capture updates.

Salesforce

We have added new system tables, FIVETRAN_ROLLUP_SUMMARY and FIVETRAN_ROLLUP_SUMMARY_FILTER, to store the Salesforce rollup summary field definitions.

These tables count towards free Monthly Active Rows (MAR).

We will no longer populate empty rollup summary field definitions into the FIVETRAN_FORMULA table from November 1, 2025.

September 2025

Connector SDK

fivetran-connector-sdk PyPI package

Schema changes

Adobe Workfront

ADP Workforce Now

Appcues

Apple App Store

Cvent

Flywheel Digital

Gladly

JustCall

Sage Intacct

Slack

Workday Financial Management

Workday HCM

Improvements

Databricks destination

FTP

Placer.ai

Salesforce

`fivetran-connector-sdk` PyPI package