Releases: fivetran/dbt_quickbooks_source
v0.10.0 dbt_quickbooks_source
🚨 Breaking Change 🚨 :
PR #51 includes the following updates:
🚘 Under the Hood
- Explicitly casts *_date fields as
date
type (due_date
,transaction_date
). Previously, some fields were getting interpreted as timestamps while some were interpreted as dates, leading to errors on downstream joins. - Updated seed files to correct timestamp formats.
This will be a breaking change to those whose source tables still use the old timestamp formats, so please update your package version accordingly.
Full Changelog: v0.9.1...v0.10.0
v0.9.1 dbt_quickbooks_source
PR #49 includes the following updates:
🎉 Features
- Added description for column
source_relation
to the documentation.
🚘 Under the Hood
- Updated partitioning in
stg_quickbooks__credit_card_payment_txn
to includesource_relation
.
Full Changelog: v0.9.0...v0.9.1
v0.9.0 dbt_quickbooks_source
This release of dbt_quickbooks_source
includes:
🎉 Feature Update 🎉
- Databricks compatibility! (#48)
Full Changelog: v0.8.0...v0.9.0
v0.8.0 dbt_quickbooks_source
🎉 Feature Updates 🎉
- Addition of the
detail_type
field within thestg_quickbooks__invoice_line
model. This field will help identify the type of invoice line in the context of the entire invoice. (PR #43)
Under the Hood
- Casted the
department_id
within the following staging models to be of type string. This ensures downstream unions on this type are consistent and of the same type. (PR #44)stg_quickbooks__bill
stg_quickbooks__bill_payment
stg_quickbooks__credit_memo
stg_quickbooks__department
stg_quickbooks__deposit
stg_quickbooks__estimate
stg_quickbooks__invoice
stg_quickbooks__journal_entry_line
stg_quickbooks__purchase
stg_quickbooks__refund_receipt
stg_quickbooks__sales_receipt
stg_quickbooks__vendor_credit
Under the Hood:
- Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. (#46) - Updated the pull request templates. (#46)
Full Changelog: v0.7.1...v0.8.0
v0.7.1 dbt_quickbooks_source
Happy National Gumdrop Day! Hope your sweet tooth gets a wonderful treat today!
Here's updates from the latest release of the new dbt_quickbooks_source
package.
🎉 Feature Updates 🎉
- Removed not-null test for
bill_payment_id
field instg_quickbooks__bill_linked_txn
to account for bills with empty bill payment values. (#41)
v0.7.0 dbt_quickbooks_source
Happy National Compliment Day everyone! Aren't you all looking great today?
You know what else is looking great? The latest release of the new dbt_quickbooks_source
package, which is filled with a host of new updates to better assist your financial reporting needs! Here's the latest updates:
🎉 🚨 Breaking Changes and New Feature 🚨 🎉:
🎉 Additional Features
- Addition of all
class_id
fields to relevant models to support adding classes upstream into your general ledger models. (#35) - Updated README to follow latest package standards. (#37)
- Added
quickbooks_[source_table_name]_identifier
variables so it's easier to refer to source tables with different names. (#37)
🦁 Contributors
dbt_quickbooks_source v0.6.0
🚨 Breaking Changes 🚨:
PR #30 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
andcurrent_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
dbt_utils.surrogate_key
has also been updated todbt_utils.generate_surrogate_key
. Since the method for creating surrogate keys differ, we suggest all users do afull-refresh
for the most accurate data. For more information, please refer to dbt-utils release notes for this update.packages.yml
has been updated to reflect new defaultfivetran/fivetran_utils
version, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.
Under the Hood
- A GitHub workflow has been added to ensure the dbt docs are regenerated before each merge to the
main
release branch.
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.
Contributors
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 latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of