v0.9.0 dbt_hubspot
Happy wednesday!
🚨 Breaking Changes 🚨
In November 2022, the Fivetran Hubspot connector switched to v3 of the Hubspot CRM API, which deprecated the CONTACT_MERGE_AUDIT
table and stored merged contacts in a field in the CONTACT
table. This has not been rolled out to BigQuery warehouses yet. BigQuery connectors with the CONTACT_MERGE_AUDIT
table enabled will continue to sync this table until the new CONTACT.property_hs_calculated_merged_vids
field and API version becomes available to them.
This release introduces breaking changes around how contacts are merged in order to align with the above connector changes. It is, however, backwards-compatible.
PR #100 applies the following changes:
- Updates logic around the recently deprecated
CONTACT_MERGE_AUDIT
table.- The package now leverages the new
property_hs_calculated_merged_vids
field to filter out merged contacts. This is the default behavior for all destinations, including BigQuery (the package will run successfully but not actually merge any contacts). This is achieved by the package's newmerge_contacts()
macro. - Backwards-compatibility: the package will only reference the old
CONTACT_MERGE_AUDIT
table to merge contacts ifhubspot_contact_merge_audit_enabled
is explicitly set totrue
in your rootdbt_project.yml
file. - The
int_hubspot__contact_merge_adjust
model (where the package performs contact merging) is now materialized as a table by default. This used to be ephemeral, but the reworked merge logic requires this model to be either a table or view.
- The package now leverages the new
Under the Hood
PR #100 applies the following changes:
- Updates seed data to test new merging paradigm.
See the source package CHANGELOG for updates made to the staging layer in dbt_hubspot_source v0.9.0
.
Full changlog: v0.8.2...v0.9.0