-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/backwards credit card #61
Conversation
…dit-card-payments
feature/credit-card-payments
swapping credit and debit accounts
…vetran/dbt_quickbooks into feature/backwards-credit-card
# version: [">=0.6.0", "<0.7.0"] | ||
- git: https://github.com/fivetran/dbt_quickbooks_source.git | ||
revision: feature/backwards-credit-card | ||
warn-unpinned: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reminder to switch before release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-joemarkiewicz Review completed!
models/double_entry_transactions/int_quickbooks__credit_card_pymt_double_entry.sql
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fivetran-joemarkiewicz PR good to go!
…vetran/dbt_quickbooks into feature/backwards-credit-card
Are you a current Fivetran customer?
Fivetran Created PR
What change(s) does this PR introduce?
Features
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. (#50)Did you update the CHANGELOG?
Does this PR introduce a breaking change?
The new model is able to be turned off via a variable and is
false
by default. As such, it will not be a breaking change.Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Is this PR in response to a previously created Bug or Feature Request
How did you test the PR changes?
Select which warehouse(s) were used to test the PR
Provide an emoji that best describes your current mood
🗃️
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.