v0.20.0 dbt_hubspot

PR #150 includes the following updates:

Upstream Breaking Changes (--full-refresh required after upgrading)

• Introduced a new category column to the following upstream models (see dbt_hubspot_source CHANGELOG notes). This association field differentiates records by either HUBSPOT_DEFINED (default label) or USER_DEFINED (custom label) and was introduced to the Hubspot connector in October 2024. See the connector release notes for more.

  • stg_hubspot__deal_company
  • stg_hubspot__deal_contact
  • stg_hubspot__engagement_company
  • stg_hubspot__engagement_contact
  • stg_hubspot__engagement_deal
  • stg_hubspot__ticket_company
  • stg_hubspot__ticket_contact
  • stg_hubspot__ticket_deal
  • stg_hubspot__ticket_engagement

• Since new columns were added upstream, a --full-refresh is needed.

Under the Hood

• Updated the respective seed files in the integration_tests folder to property test for the new category field.
• Updated seed files to make consistent with the seed files in dbt_hubspot_source.

Full Changelog: v0.19.1...v0.20.0

v0.19.1 dbt_hubspot

PR #148 includes the following updates:

Under the Hood

• Removed hubspot__daily_ticket_history, hubspot__tickets from the quickstart.yml since these models may not always be present.

Full Changelog: v0.19.0...v0.19.1

v0.19.0 dbt_hubspot

PR #147 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.

• We have made this a breaking change due to upstream changes that may alter your schema. While changes are made 'behind the scenes' to now allow models to successfully run with both hubspot__pass_through_all_columns and hubspot__<>_pass_through_columns, this may be a breaking change due to leveraging the remove_duplicate_and_prefix_from_columns macro. This is a breaking change because this macro can remove duplicate fields, resulting in an impact to your schema. For more information refer to the upstream dbt_hubspot_source v0.16.0 release notes.

Under the Hood

• Updated seed data to include fields with special syntax in order to test the above changes.

Full Changelog: v0.18.0...v0.19.0

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 return true 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.
• 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 the hubspot_contact_list_member_enabled variable in the hubspot__contact_lists model. This solves for compilation errors when the contact_list source table is not synced in the destination. If hubspot_contact_list_member_enabled is true, 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 and property_createdate datatypes in ticket_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 of contact_merge_audit.vid_to_merge to contacts.contact_id in the int_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 as true:
  -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 to false 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 for hubspot__contacts, contact_list_id for hubspot__contact_lists, deal_id for hubspot__deals, deal_stage_id for hubspot__deal_stages, and company_id for hubspot__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 and hubspot__deals models to remove stale deals that have been merged since into other deals. In addition we've introduced a new field merged_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 setting hubspot_merged_deal_enabled to True (by default this will be False). Also, hubspot_sales_enabled and hubspot_deal_enabled must not be set to False (by default these are True). See Step 4 of the README for more details.

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 the hubspot_contact_enabled variable is defined as true.
  • The int_hubspot__email_metrics__by_contact_list model is now dependent on the hubspot_contact_enabled variable being defined as true.
  • The hubspot__contact_lists model now takes into consideration the hubspot_contact_enabled variable being defined as true before joining in email metric information to the contact lists data.
• Modified the config enabled logic within the hubspot__email_sends model to be dependent on the hubspot_email_event_sent_enabled variable being true in addition to the hubspot_marketing_enabled and hubspot_email_event_enabled variables.

Under the Hood

• Added quickstart.yml for Quickstart customers.
• Added not_null tests that were previously missing to deal_id for hubspot__deals and deal_stage_id for hubspot__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 the owner source are not included when hubspot_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 variable hubspot_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

Full Changelog: v0.14.0...v0.15.0