Closed fivetran-joemarkiewicz closed 1 year ago
FYI - We will want to assess the upstream and downstream models from stg_hubspot__engagement_meeting
and ensure the variables are correct. If they are not, we will need to update those as well.
This bug has been addressed in the latest release 0.6.3. Check the release notes for more info. Closing this issue.
Is there an existing issue for this?
Describe the issue
Currently, the stg_hubspot__engagement_meeting has an incorrect variable within the enable config https://github.com/fivetran/dbt_hubspot_source/blob/198a840aa11aaf48f50e092e2c9c7a5ef21e581a/models/stg_hubspot__engagement_meeting.sql#L1
Instead of the
hubspot_engagement_email_enabled
variable being included in the model, it should instead havehubspot_engagement_meeting_enabled
.This is because the
hubspot_engagement_email_enabled
variable should only apply to the email staging models. This model however should be configured to use the relevant variable that was created for the engagement meeting (hubspot_engagement_email_enabled
).Relevant error log or model output
Expected behavior
The package uses the proper variables to disable this model.
dbt Project configurations
Package versions
What database are you using dbt with?
bigquery
dbt Version
dbt v1.2.0
Additional Context
Are you willing to open a PR to help address this issue?