PR #32 includes the following updates:
- Migrates the
union_connections,apply_source_relation, andpartition_by_source_relationmacros to thedbt_fivetran_utilspackage. - Adds the
fivetran_using_source_casingvariable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
PR #29 includes the following updates:
- Updates README with standardized Fivetran formatting.
- In the
quickstart.ymlfile:- Adds
supported_varsfor Quickstart UI customization.
- Adds
PR #27 introduces the following update:
- Limits column introspection in
pardot__campaigns(via theint__opportunity_tmpmodel) to execution time (i.e. during thedbt runanddbt build) to avoid errors duringdbt compile.
PR #26 includes the following updates:
- Increases the required dbt version upper limit to v3.0.0
PR #24 includes the following updates:
2 total changes • 1 possible breaking change
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
| All models | New column | source_relation |
Identifies the source connection when using multiple Pardot connections | |
stg_pardot__opportunity_prospect |
Updated surrogate key | opportunity_prospect_id = opportunity_id + prospect_id |
opportunity_prospect_id = source_relation + opportunity_id + prospect_id |
Updated to include source_relation |
- Union Data Functionality: This release supports running the package on multiple Pardot source connections. See the README for details on how to leverage this feature.
- Removes uniqueness tests. The new unioning feature requires combination-of-column tests to consider the new
source_relationcolumn in addition to the existing primary key, but this is not supported across dbt versions.- Note that surrogate keys are unaffected and retain their uniqueness tests.
- These tests will be reintroduced once a version-agnostic solution is available.
- Deprecated
int__opportunities_by_campaignintermediate model. The logic has been consolidated directly into thepardot__campaignsend model as a CTE for improved performance and maintainability.
PR #20 includes the following updates:
- Removed the dependency on the
fivetran/pardot_sourcepackage.- All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
- If you reference
fivetran/pardot_sourcein yourpackages.yml, you must remove this dependency to avoid conflicts. - Any source overrides referencing the
fivetran/pardot_sourcepackage will also need to be removed or updated to reference this package. - Update any pardot_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
- As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with
ref()in downstream models.
- Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g.,
unique_combination_of_columns). - Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all
dbt_utils.unique_combination_of_columnstests. - Removed all
accepted_valuestests. - Moved
loaded_at_field: _fivetran_syncedunder theconfig:block insrc_pardot.yml.
- Removed all
- Updated conditions in
.github/workflows/auto-release.yml. - Added
.github/workflows/generate-docs.yml.
- Added Quickstart model counts to README. (#18)
- Corrected references to connectors and connections in the README. (#18)
- Databricks compatibility! (#13)
- Incorporated the new
fivetran_utils.drop_schemas_automationmacro into the end of each Buildkite integration test job. (#11) - Updated the pull request templates. (#11)
PR #9 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_valuebool_orcast_bool_to_textconcatdate_truncdateadddatediffescape_single_quotesexcepthashintersectlast_daylengthlistaggpositionreplacerightsafe_castsplit_partstring_literaltype_biginttype_floattype_inttype_numerictype_stringtype_timestamparray_appendarray_concatarray_construct
- For
current_timestampandcurrent_timestamp_in_utcmacros, the dispatch AND the macro names have been updated to the below, respectively:dbt.current_timestamp_backcompatdbt.current_timestamp_in_utc_backcompat
dbt_utils.surrogate_keyhas also been updated todbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do afull-refreshfor the most accurate data. For more information, please refer to dbt-utils release notes for this update.- Dependencies on
fivetran/fivetran_utilshave been upgraded, previously[">=0.3.0", "<0.4.0"]now[">=0.4.0", "<0.5.0"].
- Updated README documentation for easier navigation and dbt package setup.
🎉 dbt v1.0.0 Compatibility 🎉
- Adjusts the
require-dbt-versionto 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_pardot_source. Additionally, the latestdbt_pardot_sourcepackage has a dependency on the latestdbt_fivetran_utils. Further, the latestdbt_fivetran_utilspackage also has a dependency ondbt_utils[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utilsin yourpackages.ymlthat is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!