Release/1.9.0#213
Conversation
* Feature re: remaining tax lines * Resolve outstanding issues * Testing tax lines * Schema * Take out tax line variable, will bring in later * Changelog, docs * Generate dbt docs via GitHub Actions * Fix compilation error * table/table doc additions --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ed data Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fivetran-joemarkiewicz
left a comment
There was a problem hiding this comment.
A few change requests and open questions before approval.
There was a problem hiding this comment.
I noticed we're not looking up any tax account in this model. Whereas the other models leveraging the tax lines join in the tax payable account to use here.
This logic currently is using the same account_id as the normal double entry method. I don't presume that's what we want to use in the tax line case.
There was a problem hiding this comment.
This was a miss from the first implementation. Updated to align with the other tax lines.
There was a problem hiding this comment.
I worry these joins could cause fan out. This tax line section also seems to behave differently from the other tax line implementations (such as bill). Is this accurate?
There was a problem hiding this comment.
Removed these joins.
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
fivetran-avinash
left a comment
There was a problem hiding this comment.
@fivetran-joemarkiewicz Changes applied. Redshift Buildkite is taking a long time (I'm still in the queue), but everything else passed, so this is good for re-review.
There was a problem hiding this comment.
This was a miss from the first implementation. Updated to align with the other tax lines.
There was a problem hiding this comment.
Removed these joins.
fivetran-joemarkiewicz
left a comment
There was a problem hiding this comment.
A few final change requests before approving
There was a problem hiding this comment.
The changes in this model need to be documented in the CHANGELOG
There was a problem hiding this comment.
Good catch. Row added to schema/data changes.
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
fivetran-avinash
left a comment
There was a problem hiding this comment.
@fivetran-joemarkiewicz changes applied, ready for final review
There was a problem hiding this comment.
Good catch. Row added to schema/data changes.
fivetran-joemarkiewicz
left a comment
There was a problem hiding this comment.
Approved with a few small requests
| | ------------- | ----------- | --- | --- | ----- | | ||
| | All tax line models | Variable configuration (opt-in) | Individual tax line variables sufficient | `quickbooks__tax_lines_enabled: true` also required | **Potential breaking change for dbt Core users** If you previously enabled any individual tax line variables, those models will now be disabled by default. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for configuration details. | | ||
| | `quickbooks__general_ledger` | Potential new rows | No tax lines | Tax lines now available (opt-in) | Tax line rows are disabled by default. Set `quickbooks__tax_lines_enabled: true` and enable individual tax line variables to post tax lines to the tax liability account. Tax lines are added only when you opt in. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for details. | | ||
| | `int_quickbooks__purchase_double_entry` | Data change | `paid_to_account_id` = purchase line expense account; `class_id` = expense class from purchase line | `paid_to_account_id` = tax liability account; `class_id` = `null` | **Potential breaking change** for users with `using_purchase_tax_line: true`. Tax lines now correctly post to the tax liability account. `class_id` is no longer populated for tax line rows. | |
There was a problem hiding this comment.
This is only relevant if the individual tax line table is enabled and quickbooks__tax_lines_enabled: true. Let's add the clarification.
There was a problem hiding this comment.
Thanks for calling that out, updated.
| [PR #213](https://github.com/fivetran/dbt_quickbooks/pull/213) includes the following updates: | ||
|
|
||
| ## Schema/Data Change | ||
| **12 total changes • 3 possible breaking changes** |
There was a problem hiding this comment.
In the sections below we use interchangeably "potential" and "possible" for breaking change callouts. Can you update either way to have consistent verbiage.
There was a problem hiding this comment.
Standardized.
Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
* feature/exchange-gain-loss * fixes * decisionlog * yml * Apply suggestion from @fivetran-catfritz * ad some aliases * convert to full * Generate dbt docs via GitHub Actions * update vars * update docs * Generate dbt docs via GitHub Actions * Apply suggestions from code review Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com> Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com> * fix seed ids * fix seed dupes * put the seeds back * restore seeds again * restore seeds again * restore seeds again * update col seed types * Generate dbt docs via GitHub Actions * merge conflicts * Update CHANGELOG with tax line model changes Updated the CHANGELOG to reflect changes in tax line models and potential breaking changes for users. Added details about enabling tax lines and configuration requirements. * Update CHANGELOG.md * Revise CHANGELOG for new features and updates Updated the CHANGELOG to reflect new features and updates regarding tax lines and exchange gain/loss entries. --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
fivetran-jamie
left a comment
There was a problem hiding this comment.
Approved pending one item
| | All tax line models | Variable configuration (opt-in) | Individual tax line variables sufficient | `quickbooks__tax_lines_enabled: true` also required | **Possible breaking change for dbt Core users** If you previously enabled any individual tax line variables, those models will now be disabled by default. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for configuration details. | | ||
| | `quickbooks__general_ledger` | Potential new rows | No tax lines | Tax lines now available (opt-in) | Tax line rows are disabled by default. Set `quickbooks__tax_lines_enabled: true` and enable individual tax line variables to post tax lines to the tax liability account. Tax lines are added only when you opt in. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for details. | | ||
| | `int_quickbooks__purchase_double_entry` | Data change | `paid_to_account_id` = purchase line expense account; `class_id` = expense class from purchase line | `paid_to_account_id` = tax liability account; `class_id` = `null` | **Possible breaking change** for users with `using_purchase_tax_line: true` and `quickbooks__tax_lines_enabled: true`. Tax lines now correctly post to the tax liability account. `class_id` is no longer populated for tax line rows. | | ||
| | `currency_id`, `exchange_rate`, `quantity`, `sales_item_quantity` in several header staging tables | Explicit type cast | Warehouse-native type | `string` / `float` | **Possible breaking change** for downstream consumers with type-sensitive logic built on staging models. | |
There was a problem hiding this comment.
string / float is a lil confusing -- are some fields strings and others floats?
There was a problem hiding this comment.
@fivetran-jamie Yep. Updated to make it clearer.
PR Overview
Package version introduced in this PR:
This PR addresses the following Issue/Feature(s):
Summary of changes:
Submission Checklist
Changelog