Releases: fivetran/dbt_hubspot
v0.18.0 dbt_hubspot
PR #144 includes the following updates:
🚨 Breaking Changes 🚨
⚠️ Since the following changes result in the table format changing, we recommend running a--full-refresh
after upgrading to this version to avoid possible incremental failures.
-
For Databricks All-Purpose clusters, incremental models will now be materialized using the delta table format (previously parquet).
- Delta tables are generally more performant than parquet and are also more widely available for Databricks users. This will also prevent compilation issues on customers' managed tables.
-
For Databricks SQL Warehouses, incremental materialization will not be used due to the incompatibility of the
insert_overwrite
strategy.
Under the Hood
- The
is_incremental_compatible
macro has been added and will returntrue
if the target warehouse supports our chosen incremental strategy.- This update was applied as there have been other Databricks runtimes discovered (ie. an endpoint and external runtime) which do not support the
insert_overwrite
incremental strategy used.
- This update was applied as there have been other Databricks runtimes discovered (ie. an endpoint and external runtime) which do not support the
- Added integration testing for Databricks SQL Warehouse.
- Added consistency tests for
hubspot__daily_ticket_history
.
Full Changelog: v0.17.2...v0.18.0
v0.17.2 dbt_hubspot
PR #142 includes the following updates:
🪲 Bug Fixes 🪛
- Fixed the
fivetran_utils.enabled_vars
conditional by adding thehubspot_contact_list_member_enabled
variable in thehubspot__contact_lists
model. This solves for compilation errors when thecontact_list
source table is not synced in the destination. Ifhubspot_contact_list_member_enabled
istrue
,int_hubspot__email_metrics__by_contact_list
is brought in as a dependency, and ignored otherwise.
🚘 Under the Hood 🚘
- Updated the
integration_tests/dbt_project.yml
variables to be global to ensure more effective testing of our seed data. - Updated
property_closed_date
andproperty_createdate
datatypes inticket_data
to cast as timestamp to fix datetime data type issues in BigQuery tests. - Updated the maintainer PR template to resemble the most up to date format.
- Removed the check docs GitHub Action as it is no longer necessary.
Full Changelog: v0.17.1...v0.17.2
v0.17.1 dbt_hubspot
PR #140 includes the following updates:
Bug Fixes
- Included explicit datatype casts to
{{ dbt.type_string() }}
within the join ofcontact_merge_audit.vid_to_merge
tocontacts.contact_id
in theint_hubspot__contact_merge_adjust
model.- This update was required to address a bug where the IDs in the join would overflow to bigint or be interpreted as strings. This change ensures the join fields have matching datatypes.
Full Changelog: v0.17.0...v0.17.1
v0.17.0 dbt_hubspot
PR #137 includes the following updates:
🚨 Breaking Changes: Variable Bug Fixes 🚨
- The following are now dependent on the
hubspot_email_event_sent_enabled
variable being defined astrue
:
-hubspot__contact_lists
email metric fields
-hubspot__contact
email metric fields
-hubspot__email_campaigns
model
-int_hubspot__email_metrics__by_contact_list
model
Note: This is a breaking change for users who have the
hubspot_email_event_sent_enabled
variable set tofalse
as this update will change the above behaviors of the package. For all other users, these changes will not be breaking.
Full Changelog: v0.16.0...v0.17.0
v0.16.0 dbt_hubspot
PR #135 includes the following updates:
🚨 Breaking Changes 🚨
- Added unique tests on
event_id
for event-based models,contact_id
forhubspot__contacts
,contact_list_id
forhubspot__contact_lists
,deal_id
forhubspot__deals
,deal_stage_id
forhubspot__deal_stages
, andcompany_id
forhubspot__companies
, on the condition the titular fields have not been deleted. We would advise running through these to ensure they work successfully.
Features
- Updates the
hubspot__deal_stages
andhubspot__deals
models to remove stale deals that have been merged since into other deals. In addition we've introduced a new fieldmerged_deal_ids
that lists all historic merged deals for each deal.- Please note you must have the underlying
merged_deals
table to take advantage of the above mentioned merged deal update. This may be enabled by settinghubspot_merged_deal_enabled
to True (by default this will be False). Also,hubspot_sales_enabled
andhubspot_deal_enabled
must not be set to False (by default these are True). See Step 4 of the README for more details.
- Please note you must have the underlying
Variable Bug Fixes
- The following adjustments have been made concerning the
hubspot_contact_enabled
variable:- The
email_events_joined()
macro now includes conditional logic to include contact information only if thehubspot_contact_enabled
variable is defined astrue
. - The
int_hubspot__email_metrics__by_contact_list
model is now dependent on thehubspot_contact_enabled
variable being defined astrue
. - The
hubspot__contact_lists
model now takes into consideration thehubspot_contact_enabled
variable being defined astrue
before joining in email metric information to the contact lists data.
- The
- Modified the config enabled logic within the
hubspot__email_sends
model to be dependent on thehubspot_email_event_sent_enabled
variable beingtrue
in addition to thehubspot_marketing_enabled
andhubspot_email_event_enabled
variables.
Under the Hood
- Added quickstart.yml for Quickstart customers.
- Added
not_null
tests that were previously missing todeal_id
forhubspot__deals
anddeal_stage_id
forhubspot__deal_stages
.
Full Changelog: v0.15.1...v0.16.0
v0.15.1 dbt_hubspot
PR #129 includes the following updates:
Bug Fixes
- Updated model
int_hubspot__deals_enhanced
so that fields from theowner
source are not included whenhubspot_owner_enabled
is set to false.
Under the Hood
- Included auto-releaser GitHub Actions workflow to automate future releases.
Full Changelog: v0.15.0...v0.15.1
v0.15.0 dbt_hubspot
PR #127 includes the following updates:
Bug fixes
- Updated variables used to determine if engagements are enabled in
hubspot__contacts
to also check variablehubspot_engagement_contact_enabled
.
Features
-
The following changes stem from changes made in the source package. See the source package v0.14.0 CHANGELOG entry for more details.
-
Added the following staging models, along with documentation and tests:
stg_hubspot__property
stg_hubspot__property_option
- These tables can be disabled by setting
hubspot_property_enabled: False
in your dbt_project.yml vars. See Step 4 of the README for more details.
-
When including a passthrough
property_hs_*
column, you now have the option to include the corresponding, human-readable labels.- The above-mentioned
property
tables are required for this feature. If you do not have them and have to disable them, unfortunately you will not be able to use this feature. - See the Adding property label section of the README for more details on how to enable this feature!
- We recommend being selective with the label columns you add. As you add more label columns, your run time will increase due to the underlying logic requirements.
- This update applies to models:
hubspot__companies
hubspot__contacts
hubspot__deals
hubspot__tickets
- The above-mentioned
Full Changelog: v0.14.0...v0.15.0
v0.14.0 dbt_hubspot
🚨 Breaking Changes 🚨
- Within the source package the
created_at
andclosed_at
fields in the below mentioned staging models have been renamed tocreated_date
andclosed_date
respectively to be consistent with the source data. Additionally, this will ensure there are no duplicate column errors when passing through allproperty_*
columns, which could potentially conflict withproperty_created_at
orproperty_closed_at
. (PR #119)stg_hubspot__company
- Impacts
hubspot__companies
- Impacts
stg_hubspot__contact
- Impacts
hubspot__contacts
- Impacts
stg_hubspot__deal
- Impacts
hubspot__deals
- Impacts
stg_hubspot__ticket
- Impacts
hubspot__tickets
- Impacts
New Model Alert 😮
Introducing Service end models! These are disabled by default but can be enabled by setting hubspot_service_enabled
to true
(PR #123):
hubspot__tickets
- Docshubspot__daily_ticket_history
- Docs- See additional configurations for the history model in README
Features
- Addition of the following variables to allow the disabling of the
*_property_history
models if they are not being leveraged. All variables aretrue
by default. (PR #122)hubspot_company_property_history_enabled
hubspot_contact_property_history_enabled
hubspot_deal_property_history_enabled
Under the Hood
- Updates to the seed files and seed file configurations for the package integration tests to ensure updates are properly tested. (PR #122)
Full Changelog: v0.13.0...v0.14.0
v0.13.0 dbt_hubspot
🚨 Breaking Changes 🚨
- This release will be a breaking change due to the removal of below dependencies.
Dependency Updates
Removes the dependencies on dbt-expectations and dbt-date. (#118)
Under the Hood
Specifically we removed the dbt_expectations.expect_column_values_to_be_unique test that was used to validate uniqueness under given conditions for the primary keys among the end models. We will be working to replace this with a similar test.
Full Changelog: v0.12.0...v0.13.0
v0.12.0 dbt_hubspot
🚨 Breaking Changes 🚨
- This release includes breaking changes as a result of upstream changes within the
v0.12.0
release of the dbt_hubspot_source package. Please see below for the relevant breaking change release notes from the source package. (PR #120) - The following models in the dbt_hubspot_source package now use a custom macro to remove the property_hs_ prefix in staging columns, while also preventing duplicates. If de-prefixed columns match existing ones (e.g.,
property_hs_meeting_outcome
vs.meeting_outcome
), the macro favors theproperty_hs_
field, aligning with the latest HubSpot API update. (PR #115)stg_hubspot__engagement_call
stg_hubspot__engagement_company
stg_hubspot__engagement_contact
stg_hubspot__engagement_deal
stg_hubspot__engagement_email
stg_hubspot__engagement_meeting
stg_hubspot__engagement_note
stg_hubspot__engagement_task
stg_hubspot__ticket
stg_hubspot__ticket_company
stg_hubspot__ticket_contact
stg_hubspot__ticket_deal
stg_hubspot__ticket_engagement
stg_hubspot__ticket_property_history
Full Changelog: v0.11.0...v0.12.0