April 2023
Apache Kafka destination
We have added Apache Kafka as one of our supported destinations. Read our Apache Kafka documentation.
You can now use Confluent Cloud as your destination with Fivetran connectors. For more information, see our setup instructions.
Fivetran GCP Indonesia Servers
We have added new servers in the Google Cloud Platform Indonesia (Jakarta) region.
You can now select Indonesia as your data processing location in your destination setup form. This means that your data doesn't leave our region-specific servers during processing. For example, if you configure your connectors to use our servers in Indonesia, your data does not leave Indonesia during processing.
For more information, see our data residency documentation.
Lite Connectors
Lite connectors are now available for the following sources:
PBF Quickstart Guide using GitHub as a source
In our new PBF Quickstart Guide, you can learn how to create a data pipeline using ConnectCard and our GitHub connector.
Schema changes
AWS Inventory
We have added the following new tables:
LAMBDA_FUNCTION
LAMBDA_LAYER
LAMBDA_VPC_SECURITY_GROUP
LAMBDA_VPC_SUBNET
We have changed the composite primary key of all tables. The new composite key is a combination of the _directory
, _file
, _line
, and _modified
columns.
Facebook Ads
We have added a new field, video_video_id
, to the CREATIVE_HISTORY
table.
Fountain
We have renamed the template_template_type
column to template_type
in the APPLICANT_SCORE_CARD_RESULT
table. To sync the historical data for this column, contact our support team.
We have removed the following tables:
AVAILABLE_SLOT
BANK
CALENDAR_BOOKED_SLOT
CALENDAR_SLOT
CALENDAR_SLOT_STAGE
GitHub
We have added the following new tables:
WORKFLOW
WORKFLOW_RUN
WORKFLOW_RUN_PULL_REQUEST
We are gradually rolling out these changes to all existing connectors.
Google Analytics 4
We have added the ITEMS_ADDED_TO_CART
and ITEMS_VIEWED
metrics to the prebuilt Ecommerce Purchases reports.
Google Display & Video 360
We have made the following schema changes to support DoubleClick Bid Manager API v2:
We have changed the labels of the following dimensions:
Dimension Old label New label FILTER_BROWSER
Browser ID
Browser
FILTER_BUDGET_SEGMENT_DESCRIPTION
Budget Segment Description
Budget Segment Name
FILTER_COMPANION_CREATIVE_ID
Video Companion Creative ID
Companion Creative ID
FILTER_COMPANION_CREATIVE_NAME
Video Companion Creative
Companion Creative
FILTER_DEVICE_MAKE
Device Make ID
Device Make
FILTER_DEVICE_MODEL
Device Model ID
Device Model
FILTER_EXTENSION
Extension
Asset
FILTER_EXTENSION_STATUS
Extension Status
Asset Status
FILTER_EXTENSION_TYPE
Extension Type
Asset Type
FILTER_GMAIL_AGE
Gmail Age
Age [FILTER_GMAIL_AGE]
FILTER_GMAIL_CITY
Gmail City
City [FILTER_GMAIL_CITY]
FILTER_GMAIL_COUNTRY
Gmail Country [FILTER_GMAIL_COUNTRY]
Country [FILTER_GMAIL_COUNTRY]
FILTER_GMAIL_COUNTRY_NAME
Gmail Country [FILTER_GMAIL_COUNTRY_NAME]
Country [FILTER_GMAIL_COUNTRY_NAME]
FILTER_GMAIL_DEVICE_TYPE
Gmail Device Type [FILTER_GMAIL_DEVICE_TYPE]
Device Type [FILTER_GMAIL_DEVICE_TYPE]
FILTER_GMAIL_DEVICE_TYPE_NAME
Gmail Device Type [FILTER_GMAIL_DEVICE_TYPE_NAME]
Device Type [FILTER_GMAIL_DEVICE_TYPE_NAME]
FILTER_GMAIL_GENDER
Gmail Gender
Gender [FILTER_GMAIL_GENDER]
FILTER_GMAIL_REGION
Gmail Region
Region [FILTER_GMAIL_REGION]
FILTER_GMAIL_REMARKETING_LIST
Gmail Remarketing List
Remarketing List [FILTER_GMAIL_REMARKETING_LIST]
FILTER_OS
Operating System ID
Operating System
FILTER_PLACEMENT_ALL_YOUTUBE_CHANNELS
Placement ID (All YouTube Channels)
Placement (All YouTube Channels)
FILTER_TRUEVIEW_AGE
Age [FILTER_TRUEVIEW_AGE]
Age (YouTube) [FILTER_TRUEVIEW_AGE]
FILTER_TRUEVIEW_CATEGORY
Category ID
Category [FILTER_TRUEVIEW_CATEGORY]
FILTER_TRUEVIEW_CITY
City Name
City [FILTER_TRUEVIEW_CITY]
FILTER_TRUEVIEW_COUNTRY
Country Name
Country (YouTube) [FILTER_TRUEVIEW_COUNTRY]
FILTER_TRUEVIEW_CUSTOM_AFFINITY
Custom Affinity ID
Custom Affinity
FILTER_TRUEVIEW_ZIPCODE
Zipcode Name
Zipcode [FILTER_TRUEVIEW_ZIPCODE]
FILTER_VIDEO_COMPANION_CREATIVE_SIZE
Video Companion Creative Size
Companion Creative Size
FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_ADVERTISER
YouTube Advertiser
Advertiser [FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_ADVERTISER]
FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER
YouTube Insertion Order
Insertion Order [FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_INSERTION_ORDER]
FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_PARTNER
YouTube Partner
Partner [FILTER_YOUTUBE_PROGRAMMATIC_GUARANTEED_PARTNER]
We have changed labels of the following metrics:
Metric Old label New label METRIC_ENGAGEMENT_RATE
Engagement Rate
Engagement Rate [METRIC_ENGAGEMENT_RATE]
METRIC_PROGRAMMATIC_GUARANTEED_IMPRESSIONS_PASSED_DUE_TO_FREQUENCY
Programmatic Guaranteed impressions passed due to frequency
Programmatic Guaranteed Bid Requests passed due to frequency
METRIC_IMPRESSION_CUSTOM_VALUE_COST
Impression custom value / cost
Custom impression value / cost
METRIC_TOTAL_IMPRESSION_CUSTOM_VALUE
Total impression custom value
Total custom impression value
We have added the following dimensions:
Dimension Label FILTER_AUDIO_FEED_TYPE_NAME
Audio Feed Type
FILTER_BID_STRATEGY_TYPE_NAME
Bid Strategy Type
FILTER_CONVERSION_AD_EVENT_TYPE
Conversion Ad Event Type
FILTER_CONVERSION_AD_EVENT_TYPE_ID
Conversion Ad Event Type ID
FILTER_EXTENSION_ASSET
Asset (upgraded)
FILTER_EXTENSION_ASSET_STATUS
Asset Status (upgraded)
FILTER_EXTENSION_ASSET_TYPE
Asset Type (upgraded)
FILTER_GUILDER_PRODUCT_ID
Sponsored Product Id
FILTER_INVENTORY_MEDIA_COST_TYPE
Inventory Media Cost Type
FILTER_MEDIA_TYPE
Media Type
FILTER_PUBLISHER_TRAFFIC_SOURCE
Publisher Traffic Source
FILTER_REFRESHED_AD_NAME
Refreshed Ad
FILTER_TARGETING_EXPANSION
Targeting Expansion
FILTER_TRUEVIEW_AD_TYPE_NAME
YouTube Ad Type
FILTER_TRUEVIEW_AUDIENCE_SEGMENT
Audience Segment
FILTER_TRUEVIEW_AUDIENCE_SEGMENT_TYPE
Audience Segment Type
FILTER_UTC_DATE
Date (UTC)
We have added the following metrics:
Metric Label METRIC_ACTIVE_VIEW_AUDIBLE_2_SEC_IMPRESSIONS
Active View: Audible (Unmuted) for 2 sec Impressions
METRIC_ACTIVE_VIEW_AUDIBLE_AND_BACKGROUND_IMPRESSIONS
Active View: Audible and Background Impressions
METRIC_ACTIVE_VIEW_PERCENT_AUDIBLE_2_SEC
Active View: % of Audible (Unmuted) for 2 sec Impressions
METRIC_ACTIVE_VIEW_PERCENT_AUDIBLE_30_SEC
Active View: % of Audible (Unmuted) for 30 sec Impressions
METRIC_ACTIVE_VIEW_PERCENT_AUDIBLE_AND_BACKGROUND
Active View: % of Audible and Background Impressions
METRIC_ACTIVE_VIEW_PERCENT_COMPLETE_AUDIBLE
Active View: % of Complete Audible Impressions
METRIC_ACTIVE_VIEW_PERCENT_EVER_MUTED
Active View: % of Ever Muted
METRIC_ACTIVE_VIEW_PERCENT_FIRST_QUARTILE_AUDIBLE
Active View: % of First Quartile Audible Impressions
METRIC_ACTIVE_VIEW_PERCENT_MIDPOINT_AUDIBLE
Active View: % of Midpoint Audible Impressions
METRIC_ACTIVE_VIEW_PERCENT_THIRD_QUARTILE_AUDIBLE
Active View: % of Third Quartile Audible Impressions
METRIC_AVERAGE_IMPRESSION_FREQUENCY_PER_USER_7DAYS
Average Impression Frequency per User (7 days)
METRIC_DEMO_COMPOSITION_IMPRESSION_COVIEWED
% Composition Impressions (Co-Viewed)
METRIC_FEE31_ADVERTISER
Advanced Ad Serving Fee (Advertiser Currency)
METRIC_FEE31_PARTNER
Advanced Ad Serving Fee (Partner Currency)
METRIC_FEE31_USD
Advanced Ad Serving Fee (USD)
METRIC_GIVT_ACTIVE_VIEW_AUDIBLE_IMPRESSIONS
General Invalid Traffic (GIVT) Active View Audible Impressions
METRIC_GRP_CORRECTED_IMPRESSIONS_COVIEWED
Impressions (Co-Viewed) [METRIC_GRP_CORRECTED_IMPRESSIONS_COVIEWED]
METRIC_IMPRESSIONS_COVIEWED
Impressions (Co-Viewed) [METRIC_IMPRESSIONS_COVIEWED]
METRIC_INACTIVE_IMPRESSIONS
Inactive Impressions
METRIC_INVALID_ACTIVE_VIEW_AUDIBLE_IMPRESSIONS
Invalid Active View Audible Impressions
METRIC_TARGET_RATING_POINTS_COVIEWED
Target Rating Points (Co-Viewed)
METRIC_UNIQUE_REACH_AVERAGE_IMPRESSION_FREQUENCY_COVIEWED
Unique Reach: Average Impression Frequency (Co-Viewed) [METRIC_UNIQUE_REACH_AVERAGE_IMPRESSION_FREQUENCY_COVIEWED]
METRIC_UNIQUE_REACH_IMPRESSION_REACH_COVIEWED
Unique Reach: Impression Reach (Co-Viewed) [METRIC_UNIQUE_REACH_IMPRESSION_REACH_COVIEWED]
METRIC_UNIQUE_REACH_TOTAL_REACH_COVIEWED
Unique Reach: Total Reach (Co-Viewed)
METRIC_VIRTUAL_PEOPLE_AVERAGE_IMPRESSION_FREQUENCY_BY_DEMO_COVIEWED
Unique Reach: Average Impression Frequency (Co-Viewed) [METRIC_VIRTUAL_PEOPLE_AVERAGE_IMPRESSION_FREQUENCY_BY_DEMO_COVIEWED]
METRIC_VIRTUAL_PEOPLE_IMPRESSION_REACH_BY_DEMO_COVIEWED
Unique Reach: Impression Reach (Co-Viewed) [METRIC_VIRTUAL_PEOPLE_IMPRESSION_REACH_BY_DEMO_COVIEWED]
METRIC_VIRTUAL_PEOPLE_IMPRESSION_REACH_PERCENT_COVIEWED
% Population Reach (Co-Viewed)
METRIC_VIRTUAL_PEOPLE_IMPRESSION_REACH_SHARE_PERCENT_COVIEWED
% Composition Reach (Co-Viewed)
We have removed the following metrics as they are no longer supported by DoubleClick Bid Manager API v2:
Dimension Label METRIC_DBM_ENGAGEMENT_RATE
Engagement Rate [METRIC_DBM_ENGAGEMENT_RATE]
METRIC_MEDIA_COST_ADVERTISER_CURRENCY_PER_STORE_VISIT_ADX_ONLY
Media Cost (Advertiser Currency) Per Store Visit (AdX only)
METRIC_REVENUE_ADVERTISER_CURRENCY_PER_STORE_VISIT_ADX_ONLY
Revenue (Advertiser Currency) Per Store Visit (AdX only)
METRIC_STORE_VISITS_ADX_ONLY
Store Visits (AdX only)
METRIC_TOTAL_MEDIA_COST_ADVERTISER_CURRENCY_PER_STORE_VISIT_ADX_ONLY
Total Media Cost (Advertiser Currency) Per Store Visit (AdX only)
HubSpot
We now use HubSpot API v1 to sync the following deprecated columns of the CONTACT_FORM_SUBMISSION
table:
conversion_id
page_url
title
Previously, we had deprecated these columns for connectors syncing the parent CONTACT
table using API v3. This change only applies to HubSpot connectors created on or after November 11, 2022, or connectors that use API v3 to sync the CONTACT
table.
Iterable
We now sync transactional_data
for events. To sync historical data for this column, contact our support team.
Marketo
We have renamed the LEAD_JOIN_MERGES
table to MERGED_LEAD
. Be sure to update your queries.
Medallia
We have added a new table, FIELD_OPTION
, which stores the options from ENUM type fields. We are gradually rolling out this change to all existing connectors.
Oracle
Now, if we detect non-specified precision or scale in your source data, we map that data to the STRING data type in your destination. Previously, we mapped it to the FLOAT data type.
PayPal
We have added the following new tables to support the Disputes resource group:
ADJUDICATION
DISPUTE
DISPUTED_TRANSACTION
DISPUTED_TRANSACTION_ITEM
DISPUTE_MESSAGE
DISPUTE_SUB_REASON
DISPUTED_TRANSACTION_ITEM_SERVICE_DETAILS_SUB_REASON
EVIDENCE
EVIDENCE_INFO_REFUND
MONEY_MOVEMENT
OFFER_HISTORY
SUPPORTING_INFO
TRACKING_INFO
We are gradually rolling out these changes to all existing connectors.
Qualtrics
We have added a new column, last_modified_date
, to the SURVEY_RESPONSE
table.
Recharge
We have upgraded our Recharge connector from version 2021-01 to 2021-11 of the Recharge API. We have made the following schema changes:
We have the added the following new tables:
ADDRESS_DISCOUNTS
CHARGE_DISCOUNT
CHARGE_ORDER_ATTRIBUTE
We have deprecated the following tables:
CHARGE_DISCOUNT_CODE
CHARGE_NOTE_ATTRIBUTE
We have added the following new columns to the tables below:
TABLE NEW COLUMNS ADDRESS
payment_method_id
andcountry_code
CHARGE
billing_address_country_code
,orders_count
, andshipping_address_country_code
CHARGE_LINE_ITEM
taxable_amount
,tax_due
,taxable
,total_price
,unit_price
, andunit_price_includes_tax
CHECKOUT
billing_address_country_code
,external_transaction_id_payment_processor
, andshipping_address_country_code
CUSTOMER
tax_exempt
ORDER
billing_address_country_code
andshipping_address_country_code
ORDER_LINE_ITEM
tax_due
,taxable
,taxable_amount
,total_price
,unit_price
, andunit_price_includes_tax
PAYMENT_METHOD
billing_address_country_code
,default
, andpayment_details
We have replaced the following columns in the tables below:
TABLE OLD COLUMN NEW COLUMN ADDRESS
cart_note
order_note
CHARGE
transaction_id
external_transaction_id_payment_processor
CHARGE
total_weight
total_weight_grams
CHARGE
number_times_tried
charge_attempts
CHARGE
shopify_variant_id_not_found
external_variant_id_not_found
CHARGE
processor_name
payment_processor
CHECKOUT
note_attributes
order_attributes
CUSTOMER
has_card_error_in_dunning
has_payment_method_in_dunning
CUSTOMER
number_active_subscriptions
subscriptions_active_count
CUSTOMER
number_subscriptions
subscriptions_total_count
ONETIME
shopify_product_id
external_product_id
ORDER_LINE_ITEM
product_title
title
We have deprecated the following columns from the tables below:
TABLE DEPRECATED COLUMNS ADDRESS
country
CHARGE
billing_address_country
,first_name
,last_charge_attempt_date
,last_name
,shipments_count
,shipping_address_country
, andsub_total
CHARGE_LINE_ITEM
price
andsubscription_id
CHECKOUT
billing_address_country
,buyer_accepts_marketing
,discount_code
, andshipping_address_country
CUSTOMER
billing_address1
,billing_address2
,billing_city
,billing_company
,billing_country
,billing_first_name
,billing_last_name
,billing_phone
,billing_province
,billing_zip
,processor_type
,reason_payment_method_not_valid
, andstatus
DISCOUNT
discount_type
,duration
,duration_usage_limit
,once_per_customer
, andtimes_used
ONETIME
recharge_product_id
andstatus
ORDER
address_is_active
,billing_address_country
,first_name
,last_name
,payment_processor
,shipping_address_country
,shipping_date
,shopify_customer_id
, andshopify_id
ORDER_LINE_ITEM
price
andsubscription_id
PAYMENT METHOD
billing_address_country
NOTE: We will re-sync all the new tables and columns to load their historical data.
Salesforce Commerce Cloud
We have added the following new columns to the COUPON_REDEMPTION
table:
creationDate
code
customerEmail
Salesforce Marketing Cloud
We have changed the primary key of the LIST_SUBSCRIBER
table and performed a table re-sync to ensure data integrity. The new composite key is a combination of the id
and list_id
columns.
Stripe
We have added a new table, INVOICE_LINE_ITEM_TAX_RATE
, to store the mappings of invoices and their associated invoice line items and tax rates. You can re-sync the INVOICE
table to backfill the INVOICE_LINE_ITEM_TAX_RATE
table for old invoices.
Workday HCM
We have added the following new tables to support the Compensation module:
BENCHMARK_AMOUNT_REPLACEMENT_DATA
BENCHMARK_JOB
BENCHMARK_JOB_AND_JOB_PROFILE
BENCHMARK_JOB_COMPOSITE_DATA
BENCHMARK_JOB_PROFILE_DATA
COMPENSATION_ALLOWANCE_PLAN_AMOUNT_PROFILE
COMPENSATION_ALLOWANCE_PLAN_PERCENT_PROFILE
COMPENSATION_ALLOWANCE_PLAN_UNIT_PROFILE
COMPENSATION_BONUS_PLAN_COVERAGE_ELIGIBILITY_RULE
COMPENSATION_BONUS_PLAN_PERFORMANCE_FACTOR_SCORECARD
COMPENSATION_BONUS_PLAN_REPLACEMENT_AMOUNT
COMPENSATION_BONUS_PLAN_REPLACEMENT_PERCENT
COMPENSATION_BONUS_TRANCHE
COMPENSATION_COMMISSION_PLAN_PROFILE
COMPENSATION_ELIGIBILITY_COMPENSATION_GRADE
COMPENSATION_ELIGIBILITY_COMPENSATION_GRADE_PROFILE
COMPENSATION_ELIGIBILITY_COMPENSATION_PACKAGE
COMPENSATION_ELIGIBILITY_COMPENSATION_PLAN
COMPENSATION_ELIGIBILITY_RULE
COMPENSATION_ELIGIBILITY_RULE_CONDITION
COMPENSATION_ELIGIBILITY_RULE_CONDITION_CATEGORY
COMPENSATION_ELIGIBILITY_RULE_COUNTRY
COMPENSATION_FUTURE_ONE_TIME_PAYMENT_PLAN
COMPENSATION_FUTURE_PAYMENT_BONUS_PLAN
COMPENSATION_MATRIX
COMPENSATION_MATRIX_AMOUNT
COMPENSATION_MATRIX_PERCENT
COMPENSATION_MATRIX_TARGET_RULE
COMPENSATION_MERIT_PLAN_REPLACEMENT_AMOUNT
COMPENSATION_MERIT_PLAN_REPLACEMENT_PERCENT
COMPENSATION_PERIOD_PLAN_PROFILE
COMPENSATION_PLAN
COMPENSATION_PLAN_ELIGIBILITY_RULE
COMPENSATION_STOCK_PLAN_AMOUNT_PROFILE
COMPENSATION_STOCK_PLAN_GRANT_SPLIT
COMPENSATION_STOCK_PLAN_PERCENT_PROFILE
COMPENSATION_STOCK_PLAN_PROFILE_GRANT_SPLIT
COMPENSATION_STOCK_PLAN_UNIT_PROFILE
DEFERRED_COMPENSATION_ELIGIBILITY_RULE
DEFERRED_COMPENSATION_PROFILE
SCORECARD
SCORECARD_GOAL
SCORECARD_PROFILE
SCORECARD_PROFILE_GOAL
We have added the following new tables to support the Payroll module:
PAY_ACCUMULATION
PAYROLL
PAYROLL_DEDUCTION_INSTANT_MESSENGER
PAYROLL_LINE
PAYROLL_LINE_PAY_COMPONENT
PAYROLL_LINE_RELATED_CALCULATION
PAYROLL_LINE_WITHHOLDING
PAYROLL_NATIONAL_ID
We now capture the data that was synced into the POSITION
table into a new table, WORKER_POSITION
. Be sure to update your queries.
We now sync the data captured from the Staffing web service into the POSITION
table and its child tables.
We have added the following child tables to the POSITION
table:
ADDITIONAL_LOCATION
ALLOWANCE_PLAN
BONUS_PLAN
CALCULATED_PLAN
COMMISSION_PLAN
JOB_PROFILE_RESTRICTION_JOB_FAMILY
JOB_REQUISITION
MERIT_PLAN
PAY_PLAN
PERIOD_SALARY_PLAN
POSITION_CERTIFICATION
POSITION_CERTIFICATION_SPECIALITY
POSITION_COMPANY_ASSIGNMENT
POSITION_COMPETENCY
POSITION_COST_CENTER_ASSIGNMENT
POSITION_CUSTOM_ORGANIZATION_ASSIGNMENT
POSITION_DOCUMENT_FIELD_RESULT
POSITION_EDUCATION
POSITION_JOB_FAMILY
POSITION_JOB_PROFILE
POSITION_JOB_PROFILE_EXEMPT
POSITION_LANGUAGE
POSITION_LANGUAGE_ABILITY
POSITION_LOCATION
POSITION_REGION_ASSIGNMENT
POSITION_RESPONSIBILITY
POSITION_STATUS
POSITION_SKILL
POSITION_TRAINING
POSITION_WORK_EXPERIENCE
POSITION_WORKER_TYPE_REFERENCE
STOCK_PLAN
UNIT_ALLOWANCE_PLAN
UNIT_SALARY_PLAN
We have removed the following columns from the POSITION
table:
academic_pay_setup_data_*
business_site_summary_*
business_title
default_weekly_hours
end_date
end_employment_date
exclude_from_headcount
federal_withholding_fein
full_time_equivalent_percentage
headcount_restriction_id
international_assignment_data_*
is_primary_job
job_exempt
job_profile_id
paid_fte
pay_rate_type
pay_through_date
payroll_interface_processing_*
position_time_type
position_title
regular_paid_equivalent_hours
scheduled_weekly_hours
specify_paid_fte
specify_working_fte
start_date
work_hours_profile
work_shift
work_space
worker_hours_profile_classification
worker_id
working_fte
working_time_frequency
working_time_unit
working_time_value
We have changed the primary keys in the following tables:
EMPLOYEE_PROBATION_PERIOD_DETAIL
POSITION
WORKER_COLLECTIVE_AGREEMENT
WORKER_POSITION_COMPENSATION
WORKER_POSITION_END_EMPLOYMENT_REASON
WORKER_POSITION_JOB_CLASSIFICATION
WORKER_POSITION_MANAGER
WORKER_POSITION_ORGANIZATION
WORKER_POSITION_PAYROLL_REPORTING_CODE
We have renamed the following tables:
COLLECTIVE_AGREEMENT
toWORKER_COLLECTIVE_AGREEMENT
COLLECTIVE_AGREEMENT_FACTOR
toWORKER_COLLECTIVE_AGREEMENT_FACTOR
CONTINGENT_WORKER_CONTRACT_INFO
toWORKER_CONTINGENT_CONTRACT
LEAVE_REQUEST_DETAIL
toWORKER_LEAVE_REQUEST_DETAIL
LEAVE_STATUS
toWORKER_LEAVE_STATUS
POSITION_END_EMPLOYMENT_REASON
toWORKER_POSITION_END_EMPLOYMENT_REASON
POSITION_JOB_CLASSIFICATION
toWORKER_POSITION_JOB_CLASSIFICATION
POSITION_PAYROLL_REPORTING_CODE
toWORKER_POSITION_PAYROLL_REPORTING_CODE
SECONDARY_TERMINATION
toWORKER_SECONDARY_TERMINATION_REASON
WORKER_MANAGER
toWORKER_POSITION_MANAGER
We will deprecate the old tables in July, 2023. However, for connectors created before April 17, 2023, we will continue to support both the old and renamed tables till we deprecate the old tables. For connectors created after April 17, 2023, the schema contains only the renamed tables.
We are gradually rolling out these changes to all existing connectors. See the Workday HCM ERD for more details.
Improvements
ADP Workforce Now
We have updated our sync strategy. We now perform a weekly historical sync to avoid data integrity issues caused by unreliable event queues from ADP.
Amazon S3
We can now sync packed JSON files from Amazon S3. We have added a new drop-down menu, JSON Delivery Mode, to the connector setup form. The drop-down menu provides you the option to choose how Fivetran should handle your JSON data. For more information, see our setup instructions.
Asana
We have added a new optional toggle, Show Advanced Options, to the connector setup form. The toggle allows you to filter the project list by team ID when you select the Synchronize specific projects sync mode. For more information, see our setup instructions.
File connectors
We now sync the values of the error cells from the Microsoft Excel file instead of syncing the errors. This change applies to the Magic Folder connectors.
Fountain
You can now configure your Fountain connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.
Lattice
You can now configure your Lattice connector using the Fivetran REST API. This feature is available only for Free, Standard, Enterprise, and Business Critical accounts.
LinkedIn Ad Analytics
We have added a new field, Historical Sync Time Frame, to the connector setup form. If you are using an existing connector, you can edit the connector and set the value. The default value is ALL_TIME
. We have also added support for the timeframe_months
field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.
Marketo
Our Marketo connectors now support table level re-syncs.
Medallia
Our Medallia connector is now generally available. Read our Medallia connector documentation.
NetSuite SuiteAnalytics
For Netsuite version 2023.1 or above, we now incrementally sync the TRANSACTION_ACCOUNTING_LINE
table to capture updates. This increases the speed of your syncs and consumes lesser MAR. For older versions, we continue to re-import this table.
Okta
We now support the following Okta domains:
okta-emea.com
okta-preview.com
Custom
Previously, we supported only the okta.com
domain. We have added a new drop-down menu, Domain, to the connector setup form. The drop-down menu provides you the option to select the domain of your Okta source. For more information, see our setup instructions.
Oracle
We now support syncing the INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND data types from your source. They appear as the STRING data type in your destination.
Sage Intacct
We have changed the new connector creation process for Sage Intacct connectors. We now use a different authentication method for Sage Intacct connectors created after April 20, 2023. We now require Sender ID and Sender Password for authentication. For more information, see our Sage Intacct Setup Guide.
We will support the existing Sage Intacct connectors that use the Fivetran-provided sender ID until April, 2024. You can also opt to migrate your existing connector to the new authentication process.
Salesforce
We now re-import the AccountTeamMember
and OpportunityTeamMember
tables to capture updates. Previously, we incrementally synced these tables. We are gradually rolling out this feature to all existing connectors.
Shopify
Shopify connectors created after April 17, 2023 use the Fivetran app by default. For more information, see our setup instructions. However, you can continue to create a connector using a non-Fivetran app (custom, private or another public app) by using the Fivetran REST API.
Square
We have changed the sync strategy for the SHIFT
table to improve the accuracy and reliability of its data. We now perform a historical sync to capture the 90-day-old historical records on a weekly basis. Even though this may temporarily slow down your syncs and increase your MAR consumption, this change in the sync strategy ensures that the data in the SHIFT
table has no discrepancies and errors.
Workday RaaS
We can now sync the nested columns in your source and sync them separately into your destination. We have added a new toggle, Enable Unpacking Nested Columns, to the connector setup form. You can set this toggle to ON to unpack and sync the nested columns. By default, we sync the nested columns as JSON objects. For more information, see our setup instructions.