v0.4.0 dbt_recharge_source

PR #21 includes the following updates:

Schema & Data Updates

4 new columns -- 2 deprecated columns -- 6 potential breaking changes

Data Model	Change Type	Old Name	New Name	Notes
stg_recharge__one_time_product	Deprecated column	_is_deleted	_is_deleted	The column will continue to persist for the time being, but we encourage referencing the _fivetran_deleted column in its place.
stg_recharge__one_time_product	New column	_fivetran_deleted		Boolean created by Fivetran to indicate whether the record has been deleted.
stg_recharge__order	Deprecated column	_is_deleted	_is_deleted	The column will continue to persist for the time being, but we encourage referencing the _fivetran_deleted column in its place.
stg_recharge__order	New column	_fivetran_deleted		Boolean created by Fivetran to indicate whether the record has been deleted. For dbt Core users: If this field is included in the recharge__order_passthrough_columns variable. It will need to be removed in order to avoid duplicate column compilation failures.
stg_recharge__charge	New column	_fivetran_deleted		Boolean created by Fivetran to indicate whether the record has been deleted. For dbt Core users: If this field is included in the recharge__charge_passthrough_columns variable. It will need to be removed in order to avoid duplicate column compilation failures.
stg_recharge__customer	New column	_fivetran_deleted		Boolean created by Fivetran to indicate whether the record has been deleted.

Documentation

• Added all new column documentation in the relevant src_recharge.yml and stg_recharge.yml files.
• Updated all the deprecated column documentation in the relevant src_recharge.yml and stg_recharge.yml files.
• Added column documentation for the billing_* fields related to the CUSTOMER source and staging models.

Under the Hood

• Included relevant updates to the impacted seed files for integration tests.
• Introduced the generate-docs github workflow for consistent docs generation.

Full Changelog: v0.3.2...v0.4.0

v0.3.2 dbt_recharge_source

This release includes the following updates.

Documentation

• Corrected references to connectors and connections in the README. (#18)

Under the Hood

• Prepends materialized configs in the package's dbt_project.yml file with + to improve compatibility with the newer versions of dbt-core starting with v1.10.0. (PR #19)
• Updates the package maintainer pull request template. (PR #20)

Contributors

• @b-per (PR #19)

Full Changelog: v0.3.1...v0.3.2

v0.3.1 dbt_recharge_source

PR #15 includes the following updates:

Bugfix

• Updated the is_most_recent_record field in stg_recharge__subscription_history to partition by id, or by subscription_id if id is unavailable in the source table. Previously, partitioning occurred solely on subscription_id (prior to applying COALESCE), which was unintended and caused errors in Redshift when the source table only contained id.

Full Changelog: v0.3.0...v0.3.1

v0.3.0 dbt_recharge_source

PR #13 includes the following updates:

Breaking Changes

• The following columns were added to model stg_recharge__address:
  • country
  • payment_method_id
  • Note: If you have already added any of these fields as passthrough columns to the recharge__address_passthrough_columns var, you will need to remove or alias these fields from the var to avoid duplicate column errors.

Features

• Added staging model stg_recharge__checkout. See this doc for the fields added and their definitions.

  • This model is disabled by default but can be enabled by setting variable recharge__checkout_enabled to true in your dbt_project.yml file. See the Enable/disable models and sources section of the README for more information.
  • This model can also be passed additional columns beyond the predefined columns by using the variable recharge__checkout_passthrough_columns. See the Passing Through Additional Columns section of the README for more information on how to set this variable.

• Added the following columns to model stg_recharge__customer. See this doc for field definitions.

  • billing_first_name
  • billing_last_name
  • billing_company
  • billing_city
  • billing_country

Under the hood

• Updated stg_recharge__subscription_history to coalesce id and subscription_id as the subscription_id since either version can be present in the source.

Full Changelog: v0.2.0...v0.3.0

v0.2.0 dbt_recharge_source

PR #12 includes the following updates:

Features

• For Fivetran Recharge connectors created on or after June 18, 2024, the ORDER source table has been renamed to ORDERS. The package will now use the ORDERS table if it exists and then ORDER if not.
  • If you have both versions but wish to use the ORDER table instead, you can set the variable recharge__using_orders to false in your dbt_project.yml.
  • See the June 2024 connector release notes and the related
    README section for more details.

Under the Hood:

• Updated the pull request templates.
• Included auto-releaser GitHub Actions workflow to automate future releases.

Full Changelog: v0.1.1...v0.2.0

v0.1.1 dbt_recharge_source

PR #10 includes the following updates:

Bug fixes

• In stg_recharge__subscription_history, updated model to use the source's updated_at column to determine the most recent record. This column is part of the primary key for the history table and is definitive, while the prior _fivetran_synced was less meaningful.

Full Changelog: v0.1.0...v0.1.1

v0.1.0 dbt_recharge_source

🎉 This is the initial release of this package! 🎉

📣 What does this dbt package do?

• Materializes Recharge staging tables, which leverage data in the format described by this ERD. These staging tables clean, test, and prepare your Recharge data from Fivetran's connector for analysis by doing the following:
  • Names columns for consistency across all packages and for easier analysis
  • Adds freshness tests to source data
  • Adds column-level testing where applicable. For example, all primary keys are tested for uniqueness and non-null values.
• Generates a comprehensive data dictionary of your Recharge data through the dbt docs site.
• These tables are designed to work simultaneously with our Recharge transformation package.
• For more information refer to the README.

Contributors

• @fivetran-poonamagate