May 2025
Schema changes
Chargebee Product Catalog 2.0
Effective May 2, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to support a feature enhancement.
15 total changes • 14 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CONTRACT_TERM | |||||
table | New Table | CONTRACT_TERM | |||
INVOICE_LINE_ITEM | |||||
column | Primary Key Change | invoice_id | invoice_id 🔑 | Added to primary key. | |
SUBSCRIPTION | |||||
column | Discontinued Column | contract_term_action_at_term_end | |||
column | Discontinued Column | contract_term_billing_cycle | |||
column | Discontinued Column | contract_term_cancellation_cutoff_period | |||
column | Discontinued Column | contract_term_contract_end | |||
column | Discontinued Column | contract_term_contract_start | |||
column | Discontinued Column | contract_term_created_at | |||
column | Discontinued Column | contract_term_id | |||
column | Discontinued Column | contract_term_object | |||
column | Discontinued Column | contract_term_remaining_billing_cycles | |||
column | Discontinued Column | contract_term_status | |||
column | Discontinued Column | contract_term_total_contract_value | |||
column | Discontinued Column | contract_term_total_contract_value_before_tax | |||
column | Rename Column | monthly_reccuring_revenue | monthly_recurring_revenue |
Dropbox Sign
Effective May 7, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to improve data management.
6 total changes • 5 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
SIGNATURE_REQUEST_CUSTOM_FIELD | |||||
column | Discontinued Column | id 🔑 | No longer a primary key. | ||
column | New Column | api_id | |||
column | Primary Key Change | index 🔑 | New primary key. | ||
SIGNATURE_RESPONSE | |||||
column | Primary Key Change | field_id 🔑 | field_id | No longer a primary key. | |
column | Primary Key Change | signature_id 🔑 | signature_id | No longer a primary key. | |
column | Primary Key Change | index 🔑 | New primary key. |
EasyPost
Effective May 12, 2025 we use a new May 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.
3 total changes • 0 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
CASH_FLOW_REPORT | |||||
table | New Table | CASH_FLOW_REPORT | |||
PAYMENT_LOG_REPORT | |||||
table | New Table | PAYMENT_LOG_REPORT | |||
SHIPMENT_INVOICE_REPORT | |||||
table | New Table | SHIPMENT_INVOICE_REPORT |
Jamf
Effective May 7, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to support a feature enhancement.
10 total changes • 2 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
COMPUTER_INVENTORY | |||||
column | New Column | disk_encryption_file_vault_2_enabled | |||
column | New Column | security_attestation_status | |||
column | New Column | security_last_attestation_attempt | |||
column | New Column | security_last_successful_attestation | |||
COMPUTER_INVENTORY_ALERT | |||||
column | New Column | class_name | |||
column | New Column | post_date | |||
COMPUTER_INVENTORY_CONFIGURATION_PROFILE | |||||
column | Primary Key Change | id 🔑 | id | No longer primary key | |
column | Primary Key Change | index 🔑 | New primary key | ||
MOBILE_DEVICE_DETAIL | |||||
column | New Column | last_attestation_attempt_date | |||
column | New Column | last_successful_attestation_date |
Mailgun
Effective May 2, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to fix a bug.
2 total changes • 2 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
INBOX_READY_DOMAIN | |||||
column | Primary Key Change | id 🔑 | id | No longer a primary key. | |
column | Primary Key Change | _fivetran_id 🔑 | New primary key. |
Proofpoint Security Awareness
Effective May 1, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to prevent or resolve data integrity issues.
1 total changes • 1 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
PHISHING_EXTENDED | |||||
column | Primary Key Change | _fivetran_id 🔑 | _fivetran_id 🔑 | Primary key calculation change. |
Rippling
Effective May 13, 2025 we use a new May 2025 schema. Review the latest ERD to better understand the schema changes. Also, see our Schema Migration article for more details.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.
We are updating the connector schema to align with source changes
35 total changes • 34 possible breaking changes
Table/column | Change type | Old name | New name | Notes | |
---|---|---|---|---|---|
WORKER | |||||
column | Discontinued Column | annual_compensation_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | annual_compensation_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_annual_salary_equivalent | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_bonus_schedule | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_created_at | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_id | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_payment_term | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_payment_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_target_annual_bonus_percent | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_updated_at | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | compensation_worker_id | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | custom_fields | Data is available in the WORKER_CUSTOM_FIELD table. | ||
column | Discontinued Column | employment_type_amount_worked | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_compensation_time_period | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_created_at | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_id | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_label | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_name | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | employment_type_updated_at | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | hourly_wage_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | hourly_wage_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | monthly_compensation_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | monthly_compensation_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | on_target_commission_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | on_target_commission_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | relocation_reimbursement_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | relocation_reimbursement_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | signing_bonus_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | signing_bonus_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | target_annual_bonus_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | target_annual_bonus_value | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | weekly_compensation_currency_type | Data is available in the WORKER_DETAILS table. | ||
column | Discontinued Column | weekly_compensation_value | Data is available in the WORKER_DETAILS table. | ||
WORKER_DETAILS | |||||
table | New Table | WORKER_DETAILS |