dbt_hubspot 0.8.0

Happy Learn Your Name In Morse Code Day! -- -.-- / -. .- -- . / .. ... / ... .... . .-. .. --..-- / .-- .... .- - .----. ... / -.-- --- ..- .-. ... ..--..

🚨 Breaking Changes 🚨:

PR #92 incorporates the following changes:

• The below models/macros have new soft deleted record flags explicitly added to them:

  • is_contact_deleted added in macros/email_events_joined which can affect the following downstream models found in models/marketing/email_events/:
    • hubspot__email_event_bounce
    • hubspot__email_event_clicks
    • hubspot__email_event_deferred
    • hubspot__email_event_delivered
    • hubspot__email_event_dropped
    • hubspot__email_event_forward
    • hubspot__email_event_open
    • hubspot__email_event_print
    • hubspot__email_event_sent
    • hubspot__email_event_spam_report
    • hubspot__email_event_status_change
  • is_deal_pipeline_deleted and is_deal_pipeline_stage_deleted added in models/sales/intermediate/int_hubspot__deals_enhanced which can affect the following downstream models found in models/sales/:
    • hubspot__deal_stages
    • hubspot__deals
  • is_deal_pipeline_deleted, is_deal_pipeline_stage_deleted and is_deal_deleted added in models/sales/hubspot__deal_stages

• Soft deleted records are also now implicitly inherited (e.g. via a select *) from the dbt_hubspot_source package's staging models and can affect the below final models (for more information, see dbt_hubspot_source PR #96):

  • Soft deleted company records (companies.is_company_deleted) included in the below models:
    • sales/hubspot__companies
  • Soft deleted deal records (deals.is_deal_deleted) included in the below models:
    • sales/hubspot__deal_stages
    • sales/hubspot__deals
  • Soft deleted contact list records (contact_lists.is_contact_list_deleted) included in the below models:
    • marketing/hubspot__contact_lists
  • Soft deleted contact records (contacts.is_contact_deleted) included in the below models:
    • marketing/hubspot__contacts
  • Soft deleted email sends records (sends.is_contact_deleted) included in the below models:
    • marketing/hubspot__email_sends

• For completeness, soft deleted records are also now included for ticket* tables, however does not currently affect this package directly and includes the following staging models:

  • stg_hubspot__ticket (is_ticket_deleted)
  • stg_hubspot__ticket_pipeline_stage(is_ticket_pipeline_stage_deleted)
  • stg_hubspot__ticket_pipeline (is_ticket_pipeline_deleted)

dbt_hubspot v0.7.0

🚨 Breaking Changes 🚨:

PR #86 includes the following breaking changes:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-refresh for the most accurate data. For more information, please refer to dbt-utils release notes for this update.
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

🎉 Features

• 🧱 Databricks compatibility! (PR #89)

dbt_hubspot v0.6.3

PR #84 incorporates the following updates:

🔧 Fixes

Added column descriptions that were missing in our documentation.

dbt_hubspot v0.6.2

Happy Thursday! 🦖

This release of the dbt_hubspot package includes the following updates:

Under the Hood

• Updated the docs as there were issues with the previous deployment. (#82)
• Introduced a GitHub workflow to ensure docs are re-built prior to merges to main. (#82)

Full Changelog: v0.6.1...v0.6.2

dbt_hubspot v0.6.1

Happy Tuesday 🌮

This release of the dbt_hubspot package includes the following updates:

Fixes

• The README had holdover merge artifacts included within it. Those artifacts have since been removed in this release. #80

Contributors

• @cristianwebber (#80)

dbt_hubspot v0.6.0

🎉 Documentation and Feature Updates

• Updated README documentation updates for easier navigation and setup of the dbt package (#67).
• Included hubspot_[source_table_name]_identifier variable for additional flexibility within the package when source tables are named differently (#67).
• Adds hubspot_ticket_deal_enabled variable (default value=False) to disable modelling and testing of the ticket_deal source table. If there are no associations between tickets and deals in your Hubspot environment, this table will not exist (#79).

🚨 Breaking Changes 🚨

• The hubspot__deal_stages model has undergone two major changes (#78):
  1. The stage and pipeline label columns now reflect where the deal was at a certain point of time (from date_stage_entered to date_stage_exited). Previously, this information reflected the deal's current stage and pipeline in every record associated with the deal.
  2. This model previously passed through all fields from the parent deals model. We removed these fields, as they are all present in hubspot__deals final model and do not change across deal stages. If you would like to join DEAL fields into the hubspot__deal_stages model, join hubspot__deal_stages with hubspot__deals on deal_id.
• Consistently renames property_dealname, property_closedate, and property_createdate to deal_name, closed_at, and created_at, respectively, in the deals model. Previously, if hubspot__pass_through_all_columns = true, only the prefix property_ was removed from the names of these fields, while they were completely renamed to deal_name, closed_at, and created_at if hubspot__pass_through_all_columns = false (#79).

dbt_hubspot v0.5.4

Happy Monday 🛌

This release of the dbt_hubspot package includes the following updates:

Fixes

• Typo fix and spelling correction within the README. (#70)
• Spelling correction of the variable names within the README. (#74)

Contributors

• @moreaupascal56 (#70, #74)

dbt_hubspot 0.5.3

Happy Tuesday!

This release of the dbt_hubspot package includes the following updates:

Under the Hood

• Added integration testing to support the new stg_hubspot__deal_contact model to the dbt_hubspot_source package.
• Updated the below models such that the respective lead() functions also account for field_name in partitions
  • hubspot__contact_history
  • hubspot__company_history
  • hubspot__deal_history
• Added test cases for the above models that can be found, respectively, in:
  • models/marketing/history/history.yml
  • models/sales/history/history.yml

dbt_hubspot v0.5.2

Happy Monday!

This release of the dbt_hubspot package includes the following updates:

Under the Hood

• Updated the engagements_joined macro to conditionally include relevant fields if their respective variables are enabled. Previously if a variable was disabled then the hubspot__engagement_calls model, which depends on the engagements_joined macro, would error out on the missing fields that were from the disabled variables. (#65)

dbt_hubspot 0.5.1

Happy Tuesday! 🌮

This release of the dbt_hubspot package includes the following updates:

Under the Hood

• Modified the join conditions within the deal_fields_joined cte of int_hubspot__deals_enhanced model to leverage the more appropriate left join rather than the using condition. This is to allow for correct and accurate joins across warehouses. (#60)