dbt_quickbooks_source v0.5.1

It's the holiday season! Happy National Gingerbread House Day 🍪 🍞 🏠 !

This newest release of the dbt_quickbooks_source package includes the following updates:

🎉 Feature Updates 🎉

• Addition of the new stg_quickbooks__credit_card_payment_txn model that may be used to track credit card transactions within QBO and used in downstream financial statement reports. (#32)

dbt_quickbooks_source v0.5.0

Happy Tuesday! 🌮

This release of the dbt_quickbooks_source package includes the following updates:

🚨 Breaking Changes 🚨

• It was discovered that IDs from the source tables can sometimes be strings. The previous build of the package interpreted all IDs as integers. To ensure the package operates as intended, the package has been updated to cast all IDs to the string datatype.
  • If you were leveraging the end models in downstream analysis, this change could break your join conditions. Be sure to be aware of any join conditions you may have downstream before upgrading your QuickBooks package. (#36) (#25) (#24)

Contributors

• @evancole-untitled (#24)

dbt_quickbooks_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 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.0 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.

Customer and Vendor Transaction Enhancements

🚧 Model Enhancement 🚧

This release includes the following non-breaking model enhancements:

• Casts the relevant customer_id and vendor_id fields to an integer which allows for seamless unioning within the downstream quickbooks__general_ledger model.

Postgres Compatibility and Address Variable

This release includes the following non-breaking changes:

• Incorporates Postgres compatibility and added Postgres testing to CircleCi. Issue #10
• Adds a variable to disable the use of the address table. Issue #11

Custom Schema and Casting Update

🚨 This update introduces a breaking change in the form of custom schemas which output staging models into a respective <target.schema> + _quickbooks_staging schema. Refer to the ReadMe for more details. 🚨

The release also:

• Casting fix of the deposit_to_account_id field within the Invoice model addressed within Issue #8
• Minor documentation updates

Sales Receipt Variable and PO Update

This release contains the following non-breaking changes:

• Included missing customer_id fields within the purchase_line models.
• Addition of purchase order models which have no downstream effects and are not used by many customers. As such, the variable for these models has by default been set to false.
• Addition of the using_sales_receipt variable for customers to disable the sales_receipt models if they are not used.

Casting Bug Fix

This release does one thing:

• Fixes a casting bug for three fields within the stg_quickbooks__invoice_line model by now casting using dbt_utils.