Releases: fivetran/dbt_quickbooks
v0.8.1 dbt_quickbooks
Happy Dr. Seuss Day everyone! Got any cats 🐱 🐈 in your hats 🎩 👒 ?
Here are the updates in the latest release of dbt_quickbooks
:
🐛 Bug Fixes 🔨
- Adding partitions by
class_id
in appropriate models to ensure correct account amount aggregations inquickbooks__general_ledger
,quickbooks__general_ledger_by_period
,quickbooks__balance_sheet
, andquickbooks__profit_and_loss
models. (#77) - Modifying join in
int_quickbooks__general_ledger_balances
to account for nullclass_id
values and bring in the correct non-zero balances. (#77)
Full Changelog: v0.8.0...v0.8.1
v0.8.0 dbt_quickbooks
Happy Singles Awareness Day! You are a strong individual coder who doesn't need another coder to show you how to run dbt packages!
Here's the latest updates from the release of dbt_quickbooks
:
🚨 Breaking Changes 🚨
- Replacing
account_name
withaccount_id
as input for thegenerate_surrogate_key
function to fixunique_id
uniqueness issues in thequickbooks__general_ledger
model. A full refresh is recommended for accurate and consistent surrogate keys. (#73)
v0.7.0 dbt_quickbooks
An unhappy National Opposite Day to you!
Another unhappy 😉 development is the release of the dbt_quickbooks
package. Thankfully, there aren't too many updates!
🚨 Breaking Changes 🚨:
- Added
transaction_source
togenerate_surrogate_key
function to fixunique_id
uniqueness issues in thequickbooks__general_ledger
model. A full refresh is recommended for accurate and consistent surrogate keys, for more information please refer to dbt-utils release notes regardinggenerate_surrogate_key
. (#62)
Additional Features
- Created the
quickbooks__cash_flow_statement
model so customers can more easily produce their own cash flow statements. Default categorizations are created inint_quickbooks__cash_flow_classifications
, where each account line is assigned acash_flow_type
, with main types beingCash or Cash Equivalents
,Operating
,Investing
, andFinancing
. Theordinal
value is also created based on thecash_flow_type
for ordering purposes. All values created are based on cash flow best practices. (#69) - For the
quickbooks__cash_flow_statement
, customers can create and configure their owncash_flow_type
andordinal
for ordering purposes. See the README for details and use the seedcash_flow_statement_type_ordinal_example
file for guidance). (#69) - Added
account_ordinal
value toquickbooks__general_ledger_by_period
,quickbooks__balance_sheet
andquickbooks__profit_and_loss
to allow customers to order their financial reports based on the account field values. The ordinals can be further configured by the customer. See the README for details and use the seedfinancial_statement_ordinal_example
file for guidance). (#65) (#66) - Added
class_id
toquickbooks__general_ledger
,quickbooks_general_ledger_by_period
, andquickbooks__balance_sheet
; add in class values for all intermediate models necessary to pass into final models. (#58). - Added
source_relation
field to all Quickbooks models to allow customers, if they have multiple Quickbooks connectors, to union them inside the package. (#62). - Added tests to all final models, particularly to test uniqueness across a combination of columns, including
source_relation
. (#62) - Modified
int_quickbooks__retained_earnings
intermediate model to accurately reflectaccount_name
field, from "Net Income / Retained Earnings Adjustment" to "Net Income Adjustment". (#66) - Updated README to follow latest package standards. (#71)
- Added
quickbooks_[source_table_name]_identifier
variables so it's easier to refer to source tables with different names. (#71)
dbt_quickbooks v0.6.0
🚨 Breaking Changes 🚨:
PR #51 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
- Dependencies on
fivetran/fivetran_utils
have been upgraded, previously[">=0.3.0", "<0.4.0"]
now[">=0.4.0", "<0.5.0"]
.
dbt_quickbooks v0.5.4
Happy Ding-A-Ling Day! ☎️ 📞 Try and catch up with friends or family you haven't talked to in awhile!
The newest, greatest release of the dbt_quickbooks
package includes the following updates:
🎉 Feature Updates 🎉
- Addition of the
credit_card_payment_txn
(enabled/disabled using theusing_credit_card_payment_txn
variable) source as well as the accompanying staging and intermediate models. This source includes all credit card payment transactions and will be used in downstream General Ledger generation to ensure accurate reporting of all transaction types. (#61)Note: the
credit_card_payment_txn
source and models are disabled by default. In order to enable them, you will want to set theusing_credit_card_payment_txn
variable totrue
in your dbt_project.yml.
Contributors
- @mikerenderco (#50, #47)
- @mel-restori (#54, #47)
dbt_quickbooks v0.5.3
Happy Wednesday! 🐫
This release of the dbt_quickbooks
package includes the following updates:
Bug Fixes
- The
int_quickbooks__bill_payment_double_entry
,int_quickbooks__credit_memo_double_entry
,int_quickbooks__deposit_double_entry
, andint_quickbooks__payment_double_entry
models perform a cross join on thestg_quickbooks__accounts
model for the respective debit/credit account. However, if this cross join includes more than one record, it will result in duplicates. An additional filter to remove sub accounts has been added to ensure the output of the models do not have duplicates. (#49)
Under the Hood
- A GitHub workflow has been added to ensure the dbt docs are regenerated before each merge to the
main
release branch. (#49)
Full Changelog: 0.5.2...0.5.3
dbt_quickbooks v0.5.2
Happy Monday 🤹♂️
This release of the dbt_quickbooks
package includes the following updates:
Bug Fixes
- Within the
v0.5.1
release, thetransaction_id
field was erroneously removed from thequickbooks__general_ledger
model. This field has since been added back. (#46)
Under the Hood
- Updated the
dbt-utils.surrogate_key()
macro to take the argument as a single list rather than a series of strings. This is to be in line with the proper use of the macro and ensure it is not impacted when the series of string argument is deprecated. (#46)
dbt_quickbooks v0.5.1
Wonderful Wednesday everyone! We have a release! 🎥
This newest release of dbt_quickbooks
includes the following updates:
Bug Fixes 🐛🪛
- Created indices for
double_entry_transactions
models. Used row_number functions forpayment
,bill_payment
andtransfer
models. (#41) - Removed transaction index on final
quickbooks__general_ledger
model, replaced by the newer indices in the sub-ledgers. (#41) - Adjusted the
bundle_income_accounts
cte within theint_quickbooks__invoice_double_entry
models to coalesce the parent and sub account id. This correctly removes any duplicate records caused from this cte in a downstream join. (#42)
dbt_quickbooks v0.5.0
Happy Tuesday! 🌮
This release of the dbt_quickbooks
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)
quickbooks 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_quickbooks_source
. Additionally, the latestdbt_quickbooks_source
package has a dependency on the latestdbt_fivetran_utils
. Further, 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