v0.8.0 dbt_xero

PR #54 includes the following updates:

Bug Fixes

• Fixed the _credit_note and _bank_transaction table variable naming in quickstart.yml to ensure their respective models are enabled and disabled appropriately.
• We've made this release a breaking change to highlight to all Quickstart customers that this will have an impact on their model counts if either of these tables are selected in the schema tab and present in their destination.

Full Changelog: v0.7.0...v0.8.0

v0.7.0 dbt_xero

PR #54 includes the following updates:

Breaking Changes

• Corrected the calculation of current_year_end_date in the xero__balance_sheet_report model. Previously, current_year_end_date was miscalculated in certain scenarios, impacting the classification of records with the account_name value "Retained Earnings."
  • This is labeled as a breaking change since it may affect prior labels assigned. We recommend reviewing your records to ensure they align with this corrected logic.

Bug Fixes

• Updated the xero__balance_sheet model to resolve a run error when an organization's financial year end date is February 29.

Documentation

• Updated README formatting for consistency with other packages.
• Added Quickstart model counts to README. (#52)
• Corrected references to connectors and connections in the README. (#52)

Under the Hood (maintainers only)

• Added consistency tests for the end models.

Full Changelog: v0.6.2...v0.7.0

v0.6.2 dbt_xero

PR #46 includes the following updates:

Bug Fixes

• Update to the xero__balance_sheet model to ensure the calculated current_year_end_date field takes into account fiscal year ends which occur in a leap year. To address this, if a lookback is required, then February 28th of the previous year will be used to ensure a valid date is used.

Under the Hood

• Included auto-releaser GitHub Actions workflow to automate future releases.
• Updated the maintainer PR template to resemble the most up to date format.

Full Changelog: v0.6.1...v0.6.2

v0.6.1 dbt_xero

PR #40 includes the following updates:

Test Updates

• The unique combination of columns test within the xero__general_ledger model has been updated to include journal_id in addition to journal_line_id and source_relation.
  • This update is required as deleted journals may still appropriately be rendered in the general ledger; however, they will have no associated journal lines. As such, there may be unique journal_ids with a null journal_line_id. This test update will account for this scenario.

Contributors

• @jsagasta (PR #40)

Full Changelog: v0.6.0...v0.6.1

v0.6.0 dbt_xero

This release of dbt_xero includes:

🎉 Feature Update 🎉

• Databricks compatibility! (#38)

🚘 Under the Hood 🚘

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#37)
• Updated the pull request templates. (#37)

Full Changelog: v0.5.0...v0.6.0

dbt_xero v0.5.0

🚨 Breaking Changes 🚨:

PR #33 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_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_xero 0.4.2

Happy Thursday! 🎉

Bug Fix

• Fixes duplicate values in net_amount field in xero__balance_sheet_report when leveraging logic to union multiple Xero connectors

Contributors

• @danieltaft #30

dbt_xero 0.4.1

Happy Thursday!

This release of the dbt_xero package includes the following updates:

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

• @santi95 (#27)

dbt_xero 0.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 0.3.1

Happy Friday!

This release of the dbt_xero package contains the following changes:

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. (#22)
  • 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.