The union_schema and union_database variables have been renamed to xero_union_schema and xero_union_database respectively. This helps to keep these variables unique and mitigates the risk of the same variable being referenced within your dbt project.
Features
The README documentation has been updated to provide a better walkthrough of how to effectively leverage the dbt package.
The sql and jinja style has been updated to remain consistent with our sql style guide.
Additional xero__<default_source_table_name>_identifier variables have been added to enable users to more easily point the dbt package at different named source tables.
Under the Hood
All datetime fields have been cast using {{ dbt_utils.type_timestamp() }} to ensure downstream date operation succeed across all warehouses.
Did you update the CHANGELOG?
[X] Yes
Does this PR introduce a breaking change?
[X] Yes (please provide breaking change details below.)
[ ] No (please provide an explanation as to how the change is non-breaking below.)
See details in the changelog above.
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
[ ] Yes, Issue/Feature [link bug/feature number here]
[X] No
How did you test the PR changes?
[X] CircleCi
[ ] 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
✍️
**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?
Fivetran created PR
What change(s) does this PR introduce?
🎉 Documentation and Style Standards Update 🎉
🚨 Breaking Changes 🚨
union_schemaandunion_databasevariables have been renamed toxero_union_schemaandxero_union_databaserespectively. This helps to keep these variables unique and mitigates the risk of the same variable being referenced within your dbt project.Features
xero__<default_source_table_name>_identifiervariables have been added to enable users to more easily point the dbt package at different named source tables.Under the Hood
{{ dbt_utils.type_timestamp() }}to ensure downstream date operation succeed across all warehouses.Did you update the CHANGELOG?
Does this PR introduce a breaking change?
See details in the changelog above.
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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.