Releases: fivetran/dbt_quickbooks
v0.12.4 dbt_quickbooks
PR #123 includes the following updates:
Bug Fixes
- Added
source_relation
to joins within the following models as it was previously missed:int_quickbooks__invoice_join
int_quickbooks__bill_join
int_quickbooks__refund_receipt_double_entry
int_quickbooks__sales_receipt_double_entry
quickbooks__balance_sheet
analysis model.
Contributors
Full Changelog: v0.12.3...v0.12.4
v0.12.3 dbt_quickbooks
PR #119 includes the following updates:
Bug Fixes
- Included a default start and end date in the
int_quickbooks__general_ledger_date_spine
logic when generating the date spine. These default start and end dates will ensure the model still succeeds when no transactions are yet available.- The default start date will be one month in the past
- The default end date will be the current date
Under the Hood
- Updated the maintainer PR template to resemble the most up to date format.
- Removed the check docs GitHub Action as it is no longer necessary.
Full Changelog: v0.12.2...v0.12.3
v0.12.2 dbt_quickbooks
PR #114 includes the following updates:
Bug Fixes
- Updated model
int_quickbooks__invoice_double_entry
to account for thesales_item_account_id
field from theinvoice_lines
source when determining theaccount_id
associated with an invoice.
Full Changelog: v0.12.1...v0.12.2
v0.12.1 dbt_quickbooks
PR #109 includes the following updates:
Bug Fixes
- Adjusted the joins within the below intermediate double entry models to be
left join
as opposed to aninner join
. This update was necessary as there was the possibility of the respective account cte joins to return no records. If this was the case, the logic could erroneously remove transactions from the record.
Full Changelog: v0.12.0...v0.12.1
v0.12.0 dbt_quickbooks
PR #103 includes the following updates:
🚘 Under the Hood
- Update seeds and configs in the integration tests folder to match what was updated upstream in the (source package PR #51) to correct timestamp fields that should be date fields (
due_date
,transaction_date
). Previously, some fields were getting interpreted as timestamps while some were interpreted as dates, leading to errors on downstream joins. In the upstream staging models,due_date
andtransaction_date
are now explicitly cast asdate
types.
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.11.1...v0.12.0
v0.11.1 dbt_quickbooks
This release of dbt_quickbooks
includes the following updates:
🐛 Bug Fixes 🩹
- Updated intermediate double entry models that have
account_type
andaccount_sub_type
filters with configurable variables, since the type names used in the filter can be adjusted internally by QuickBooks customers. (#98) - Includes
items.asset_account_id
as the second field of the coalesce for thepayed_to_account_id
field within theint_quickbooks__bill_payment_double_entry
model to ensure all account_id types are taken into consideration when mapping the transaction to the proper account. (#100)
🎉 Feature Updates 🎉
- The intermediate models where these variables were introduced in the models below (#98):
Updated model | New variables to filter on |
---|---|
int_quickbooks__bill_payment_double_entry | quickbooks__accounts_payable_reference |
int_quickbooks__credit_memo_double_entry | quickbooks__accounts_receivable_reference |
int_quickbooks__deposit_double_entry | quickbooks__undeposited_funds_reference |
int_quickbooks__invoice_double_entry | quickbooks__sales_of_product_income_reference , quickbooks__accounts_receivable_reference |
int_quickbooks__payment_double_entry | quickbooks__accounts_receivable_reference |
🗒️ Documentation
- Updated README with additional steps for configuration. This is an optional step since most customers will rely on the default account type/subtype values available.
Contributors
Full Changelog: v0.11.0...v0.11.1
v0.11.0 dbt_quickbooks
🚨 Breaking Changes 🚨
PR #95 includes the following updates:
🪲 Bug Fixes
- Included
source_relation
in all joins and window functions for models outputtingsource_relation
. This is to prevent duplicate records in end models when using the unioning functionality. These updates were in the intermediate models, which flowed to downstream end models:quickbooks__general_ledger
quickbooks__expenses_sales_enhanced
- In end model
quickbooks__general_ledger
, addedsource_relation
as part of the generated surrogate keyunique_id
to prevent duplicateunique_id
s when using the unioning functionality.
🎉 Features
- Added description for column
source_relation
to the documentation.
🚘 Under the Hood
- Updated test from a combination of columns to uniqueness of
unique_id
inquickbooks__general_ledger
. - Updated partitioning in certain models to include
source_relation
. - Updated analysis
quickbooks__balance_sheet
with updated join strategy.
Full Changelog: v0.10.0...v0.11.0
v0.10.0 dbt_quickbooks
This release of dbt_quickbooks
includes:
🎉 Feature Update 🎉
- Databricks compatibility! (#92)
Full Changelog: v0.9.1...v0.10.0
v0.9.1 dbt_quickbooks
PR #93 includes the following updates:
Bug Fixes
- Adjusted the purchase amount totals within the
int_quickbooks__purchase_transactions
model to factor in credits when calculating purchase amounts.
Full Changelog: v0.9.0...v0.9.1
v0.9.0 dbt_quickbooks
Bug Fixes
- Added logic to the
int_quickbooks__invoice_double_entry
model to account for invoice discounts as they should be treated as contra revenue accounts that behavior differently from normal sale item detail invoice line items. (#85) - Updated the
cash_beginning_period
andcash_net_period
values to coalesce to 0 in thequickbooks__cash_flow_statement
in order to ensure every row has a value, especially the first row in the sequence since it will always be null. (#88)
Additional Features
- Added
department_id
to thequickbooks__general_ledger
and the upstream tables required for that change. (#63)- Please note that this field was not added to the downstream
quickbooks__general_ledger_by_period
,quickbooks__balance_sheet
,quickbooks__profit_and_loss
, orquickbooks__cash_flow_statement
models as this would require the grain of these models to be adjusted for thedepartment_id
. This would likely cause more confusion in the initial output. As such, the field was omitted in the aggregate models to ensure consistency of these models. If you wish this to be included, please open a Feature Request to let us know!
- Please note that this field was not added to the downstream
Documentation
- Included documentation within the DECISIONLOG centered around the behavior of how invoice discounts are handled within the
int_quickbooks__invoice_double_entry
model. (#85)
Under the Hood
- Leveraged the new
detail_type
field to ensure better accuracy when identifying invoice lines that should be accounted for in the general ledger calculations. (#85) - Incorporated the new
fivetran_utils.drop_schemas_automation
macro into the end of each Buildkite integration test job. (#87) - Updated the pull request templates. (#87)
Complimentary Release Notes
- See the source package CHANGELOG for updates made to the staging layer in
dbt_quickbooks_source v0.8.0
.
Contributors
Full Changelog: v0.8.1...v0.9.0