Releases: fivetran/dbt_hubspot_source
dbt_hubspot_source v0.5.4
dbt_hubspot_source 0.5.3
Happy Tuesday! 🌮
This release of the dbt_hubspot_source
package includes the following updates:
Under the Hood
- Cast the
deal_pipeline_stage_id
anddeal_pipeline_id
fields within the stg_hubspot__deal_pipeline, stg_hubspot__deal_pipeline_stage, stg_hubspot__deal using thedbt_utils.type_string()
macro. This ensures joins in downstream models are accurate across warehouses. (#57)
dbt_hubspot_source 0.5.2
Updates
- Removing unused models
stg_hubspot__engagement_email_cc
andstg_hubspot__engagement_email_to
fromstg_hubspot__engagement.yml
(#56)
Contributors
- @ericalouie (#60).
dbt_hubspot_source 0.5.1
Updates
- Updating
README.md
to reflect global variable references indbt_project.yml
to be consistent withdbt_hubspot
package.
Contributors
dbt_hubspot_source v0.5.0
🎉 dbt v1.0.0 Compatibility 🎉
🚨 Breaking Changes 🚨
- Adjusts the
require-dbt-version
to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.- For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
- For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
- Upgrades the package dependency to refer to the latest
dbt_fivetran_utils
. The latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
Calculated Fields and Engagement Task Fix
Happy Tuesday!
This release of the dbt_hubspot_source Fivetran dbt package includes the following non-breaking changes and updates:
- Addition of the
hubspot__deal_calculated_fields
,hubspot__company_calculated_fields
,hubspot__contact_calculated_fields
, andhubspot__ticket_calculated_fields
calculated field variables to allow users to define and pass their own calculated fields through the staging models. - Correction within
stg_hubspot__engagement_task
model to only perform thesafe_cast
util on thecompletion_date
if the field is not already a timestamp. The conditional logic applied checks the datatype of the field, and if the field is not a UTC timestamp then it will safe cast accordingly.
Huge shoutout to @joellabes for bringing up the calculated fields variable idea and @brettkobo for raising the timestamp casting to our attention! 🎉
Contact Merge Audit Table Addition
🚧 Contact Merge Audit Table Addition 🚧
This release includes the following non-breaking changes:
- Addition of the
stg_hubspot__contact_merge_audit
model which is disabled by default. This model can be used to resolve merged contacts that are persisting within the source contact table in downstream models.
Reintroduce ability to pass through all columns
Hello fellow modelers! 🤠
This release addresses issue #44, which raised the very valid point that having to explicitly pass through potentially hundreds of columns is very annoying! Thus, this release reintroduces the old behavior of passing through all columns from the DEAL
, COMPANY
, CONTACT
, and TICKET
tables.
To implement this, set the hubspot__pass_through_all_columns
variable to true
in your dbt_project.yml
file (by default this is false
).
More details can be found in the README.
dbt 0.20.0 Compatibility
🎉 dbt 0.20.0 Compatibility 🎉
🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.
Additional considerations when upgrading to this package:
- This package utilizes the latest
v0.7.0
release of thedbt-labls/dbt_utils
package. If your project also utilizes a version of thefishtown-analytics/dbt_utils
package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package. - Similar to the above point, all previous Fivetran dbt packages utilize the
fishtown-analytics/dbt_utils
package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.
Fivetran Utils Dependency Update
🚧 Fivetran Utils Dependency Update 🚧
This release includes the following non-breaking changes:
- Update to the
packages.yml
to reference the recently released Fivetran Utils package. This is a necessary update to ensure this package is compatible with previous dbt releases before dbt v0.20.0 updates take place.