Skip to content

Latest commit

 

History

History
36 lines (29 loc) · 3.43 KB

CHANGELOG.md

File metadata and controls

36 lines (29 loc) · 3.43 KB

dbt_xero v0.4.1

Features

  • Adds the xero__using_bank_transaction variable to disable the associated models on instances of Xero that don't include the bank_transaction source table. (#27)

Contributors

dbt_xero v0.4.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_xero_source. Additionally, the latest dbt_xero_source package has a dependency on the latest dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
    • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt_xero v0.3.1

Bug Fix

  • The account_code, account_id, account_name, and account_type fields within the xero_general_ledger are now being selected from the stg_xero__account model instead of the stg_xero__journal_line model.
    • It was found that account names may be changed within Xero, but the account name within a journal line entry will remain the old name. As such, this fix will ensure all records on the xero__general_ledger and downstream models reflect the most up to date name of the account.

dbt_xero v0.3.0

Features

  • Allow for multiple sources by unioning source tables across multiple Xero connectors. (#11)
    • Refer to the unioning multiple Xero connectors section of the README for more details.

Under the Hood

  • Unioning: The unioning occurs in Xero source package using the fivetran_utils.union_data macro. (#16)
  • Unique tests: Because columns that were previously used for unique tests may now have duplicate fields across multiple sources, these columns are combined with the new source_relation column for unique tests and tested using the dbt_utils.unique_combination_of_columns macro. (#16)
  • Source Relation column: To distinguish which source each field comes from, we added a new source_relation column in each staging model and applied the fivetran_utils.source_relation macro. (#16)
  • Utils Materialization: We have made the default materialization of the utils folder to be ephemeral. (#16)

dbt_xero v0.1.0 -> v0.2.0

Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!