π π¨ Breaking Changes and New Feature π¨ π:
Add union schema ability to run QuickBooks across a number of schemas. #35. Thanks to @ligfx for putting in the hard work that inspired this 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
Did you update the CHANGELOG?
[x] Yes
Does this PR introduce a breaking change?
[x] Yes (please provide breaking change details below.)
See above
[ ] No (please provide an explanation as to how the change is non-breaking below.)
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)
[x] Yes
Is this PR in response to a previously created Bug or Feature Request
[x] Yes, see above
[ ] No
How did you test the PR changes?
[x] BuildKite
[ ] Local (please provide additional testing details below)
Select which warehouse(s) were used to test the PR
[x] BigQuery
[x] Redshift
[x] Snowflake
[x] Postgres
[ ] Databricks
[ ] Other (provide details below)
Provide an emoji that best describes your current mood
:trumpet:
**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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.
Are you a current Fivetran customer?
What change(s) does this PR introduce?
π π¨ Breaking Changes and New Feature π¨ π:
π Additional Features
class_id
fields to relevant models to support adding classes upstream into your general ledger models. #35quickbooks_[source_table_name]_identifier
variables so it's easier to refer to source tables with different names. #37Did you update the CHANGELOG?
Does this PR introduce 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
:trumpet: **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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.