Closed leinemann closed 1 year ago
This is something that would be of use to me too!
I have two quickbooks connectors feeding into the same warehouse (ours happens to be PSQL in AWS). They are written to different schemas (ab_quickbooks, ab_cd_quickbooks) though. I only really care about the Quickbooks reports (e.g. P&L, BS), which are run through this module in DBT.
Currently, I have to go through some work-arounds in order to get both of these running correctly, namely changing my ~/.dbt/profiles.yml
file and using command line vars to repoint schemas. I'd love to just use a single command or single line config in deployment.yml
to select which transformation job I'm running.
Hi @leinemann and @mcgodes thanks for creating this Feature request and also commenting that this would be of use to you both!
It has been a while, but our team is currently in the process of taking on this feature in a future update to the dbt package! You can see the work being done within PR #62. This will be a post dbt-utils v1.0.0 migration update, but you should see this live within the package before the end of January!
Hi @leinemann and @mcgodes , thanks again for all your assistance in prioritizing this upgrade!
We have added support for multiple quickbooks instances and sources in the 0.7.0
version of the package.
Instructions are available in the README under Step 5: Additional Configurations in the Unioning Multiple Quickbooks Connectors section.
If you update your packages.yml
to reference this version (or any versions beyond that, as we've recently bumped it up to 0.8.0), you should be able to support multiple sources in this manner.
We're going to go ahead and close this issue, but if you have any questions, thoughts or feedback, feel free to leave them in this issue and we'll be happy to respond.
Enjoy unioning all your sources!
Are you a Fivetran customer? Christoph, sustain.life
Is your feature request related to a problem? Please describe. We are currently unable to created top level/unified models across several quickbooks instances/accounts.
Describe the solution you'd like I'd love to see a solution in line with what has been done for shopify / xero already to support unionizing across multiple sources.
Describe alternatives you've considered rather hackie, one-off consolidation / macros that combine uniform tables from several schemata.
Additional context as per slack discussion: https://getdbt.slack.com/archives/C01D1R2JLLA/p1642096997045200
Please indicate the level of urgency and business impact of this request huge value to our finance folks.
Are you interested in contributing to this package?