v0.6.0 dbt_xero_source

This release of dbt_xero_source includes:

🎉 Feature Update 🎉

• Databricks compatibility! (#20)

🚘 Under the Hood 🚘

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

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

dbt_xero_source v0.5.0

🚨 Breaking Changes 🚨:

PR #17 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_source 0.4.1

Happy Thursday!

This release of the dbt_xero_source 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 that bank_transaction source table. (#15)

Contributors

• @santi95 (#15)

dbt_xero_source 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_fivetran_utils. 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_source v0.3.0

🎉 New Feature 🎉

This v0.3.0 release includes the following non-breaking changes. Please refer to the CHANGELOG for additional information.

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!(#11 )

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Fivetran Utils Dependency Update

🚧 Fivetran Utils Dependency Update 🚧

This release includes the following non-breaking changes:

• Update to the packages.yml to reference the recently released Fivetran Utils package. This is a necessary update to ensure this package is compatible with previous dbt releases before dbt v0.20.0 updates take place.

Credit Note Model Variable Addition

🐞 Bug Fix 🐞

This release introduces the followning non-breaking bug fixes:

• The addition of the xero__using_credit_note variable to disable the credit_note models if a user does not have them in their source.

Feature: Add Credit Note and Bank Transaction staging tables

This Release introduces the addition of the Credit Note and Bank Transaction staging tables.

Having these new tables will allow us to add a contact_id field to the general ledger model in the transformation package.

Initial Release

This is the initial release of this package.

This package enables you to better understand your Xero reporting data.

Currently the package supports Redshift, BigQuery, Postgres and Snowflake.