[Bug] <General Ledger/Balance Sheet accounts Don't balance because there are no entries for Credit Card Payments>

[mikerenderco]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the issue

We created a Balance Sheet from the General Ledger and we have also pulled the Balance Sheet that is provided. Fivetrans has the Quickbooks Table pulling in a table called credit_card_payment_txn. When you try to balance a Credit Card Account or the Cash account from a bank account from the General Ledger and the Balance these two accounts will always be off by the amounts in the credit_card_payment_txn table.

It seems like these need to be entries in the General Ledger.

Relevant error log or model output

No response

Expected behavior

The expected behavior is to have all accounts balance from the general_ledger and the balance_sheet that this code produces.

dbt Project configurations

This is the standard configuration.

Package versions

packages:

• package: fivetran/quickbooks version: [">=0.5.1", "<0.6.0"]

What database are you using dbt with?

bigquery

dbt Version

DBT Cloud Environment

Additional Context

No response

Are you willing to open a PR to help address this issue?

• [ ] Yes.
• [ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
• [X] No.

[fivetran-joemarkiewicz]

Hi @mikerenderco thanks for opening this issue!

I agree that in this situation including the credit_card_payment_txn source table into our General Ledger (and other financial statement) downstream models would account for the differences you are currently seeing. The data we used to develop and maintain this package actually does not leverage the credit_card_payment_txn table and therefore was not included in the original build of the package.

However, we are happy to consider adding the table. In order to do so, I am curious if you would be open to sharing more details about this table. For example, do you have sample data (could be a few hashed records within a .csv) that you would be comfortable sharing for our development efforts? Additionally, can you confirm that this table contains all the required information to fold into the downstream financial statements, or are there additional joins (outside of the account joins) that you believe would need to be factored in?

Let me know your thoughts. We would be happy to incorporate this model, but want to make sure we are making correct updates before jumping into the new table and downstream models.

[mikerenderco]

@fivetran-joemarkiewicz great points here. I don't know that the credit_card_payment_txn contains all the fields you would need to build data into the GL and Balance Sheet. What I ended up doing for our client is union-ing to additional tables in Big query to the GL. I have attached our table with example records. quickbooks.credit_card_payment_txn.csv Also here is where the SQL that I was using built off of this table to build a view that contains your GL (Plus Class info) and unioning two other tables - 1 for the credit card account debit and 1 for the bank account debit. Please note this is standard sql from big query.

Select t1.unique_id,t1.transaction_id, t1.transaction_index,t1.transaction_date,t1.customer_id,t1.vendor_id,t1.amount,t1.account_id, t1.account_number, t1.account_name,t1.is_sub_account,t1.parent_account_number,t1.account_type,t1.account_sub_type,t1.financial_statement_helper,t1.account_current_balance,t1.account_class,t1.transaction_type,t1.transaction_source,t1.account_transaction_type,t1.adjusted_amount,t1.running_balance, case when t1.transaction_source = 'journal_entry' then t2.fully_qualified_name when t1.transaction_source = 'purchase' then t3.fully_qualified_name when t1.transaction_source = 'bill' then t4.fully_qualified_name when t1.transaction_source = 'deposit' then t5.fully_qualified_name --when t1.transaction_source = 'bill_payment' then t6.fully_qualified_name when t1.transaction_source = 'vendor_credit' then t7.fully_qualified_name when t1.transaction_source = 'invoice' then t8.fully_qualified_name when t1.transaction_source = 'sales_receipt' then t9.fully_qualified_name else null END as FullyQualifiedClassName, case when t1.transaction_source = 'journal_entry' then t2.name when t1.transaction_source = 'purchase' then t3.name when t1.transaction_source = 'bill' then t4.name when t1.transaction_source = 'deposit' then t5.name --when t1.transaction_source = 'bill_payment' then t6.name when t1.transaction_source = 'vendor_credit' then t7.name when t1.transaction_source = 'invoice' then t8.name when t1.transaction_source = 'sales_receipt' then t9.name else null END as ClassName, last_day(t1.transaction_date) AS period_end_date

From qb_quickbooks.quickbooks__general_ledgert1

--JOURNAL ENTRY JOIN left join quickbooks_custom_views.je_summary t2 on t1.transaction_source = 'journal_entry' and t1.transaction_id = t2.journal_entry_id and t1.transaction_index = t2.index

--PURCHASE JOIN left join quickbooks_custom_views.purchase_summary t3 on t1.transaction_source = 'purchase' and t1.transaction_id = t3.purchase_id and t1.transaction_index = t3.index

--BILL JOIN left join quickbooks_custom_views.bill_summary t4 on t1.transaction_source = 'bill' and t1.transaction_id = t4.bill_id and t1.transaction_index = t4.index

--DEPOSIT JOIN left join quickbooks_custom_views.deposit_summary t5 on t1.transaction_source = 'deposit' and t1.transaction_id = t5.deposit_id and t1.transaction_index = t5.index

--BILL PAYMENT JOIN --left join quickbooks_custom_views.bp_summary t6 on t1.transaction_source = 'bill_payment' and t1.transaction_id = t6.bill_payment_id and t1.transaction_index = t6.index

--VENDOR CREDIT PAYMENT JOIN left join quickbooks_custom_views.vc_summary t7 on t1.transaction_source = 'vendor_credit' and t1.transaction_id = t7.vendor_credit_id and t1.transaction_index = t7.index

--INVOICE PAYMENT JOIN left join quickbooks_custom_views.invoice_summary t8 on t1.transaction_source = 'invoice' and t1.transaction_id = t8.invoice_id and t1.transaction_index = t8.index

--SALES RECEIPT PAYMENT JOIN left join quickbooks_custom_views.sr_summary t9 on t1.transaction_source = 'sales_receipt' and t1.transaction_id = t9.sales_receipt_id and t1.transaction_index = t8.index

where t1.unique_id not in (select unique_id from qb_quickbooks.quickbooks__general_ledger where account_number ='1010' and transaction_source = 'bill payment' and transaction_index=1)

UNION ALL --Credit Card Payment Cedit Card Account General Ledger Transactions

Select GENERATE_UUID() as unique_id, t1.id as transaction_id, 0 as transaction_index, t1.transaction_date, null as customer_id, null as vendor_id, t1.amount, t1.credit_card_account_id as account_id, '2104' as account_number, 'Credit Card' as account_name, false as is_sub_account, '2104' as parent_account_number, 'Cradit Card' as account_type, 'CreditCard' as account_sub_type, 'balance_sheet' as fincial_statement_helper, (select max(account_current_balance) From quickbooks_custom_views.general_ledger where account_number ='2104') as account_current_balance, 'Liability' as account_class, 'credit' as transaction_type, 'credit_card_payment' as transaction_source, 'credit' as account_transaction_type, -t1.amount as adjusted_amount, 0 as running_balance, null as FullyQualifiedClassName, null as ClassName, last_day(t1.transaction_date) AS period_end_date From quickbooks.credit_card_payment_txn t1

union all

--Credit Card Payment Bank Account General Ledger Transactions Select GENERATE_UUID() as unique_id, t1.id as transaction_id, 0 as transaction_index, t1.transaction_date, null as customer_id, null as vendor_id, t1.amount, t1.bank_account_id as account_id, '1010' as account_number, 'BOK Checking (3276)' as account_name, false as is_sub_account, '1010' as parent_account_number, 'Bank' as account_type, 'Checking' as account_sub_type, 'balance_sheet' as fincial_statement_helper, (select max(account_current_balance) From quickbooks_custom_views.general_ledger where account_number ='1010') as account_current_balance, 'Asset' as account_class, 'debit' as transaction_type, 'credit_card_payment' as transaction_source, 'debit' as account_transaction_type, -t1.amount as adjusted_amount, 0 as running_balance, null as FullyQualifiedClassName, null as ClassName, last_day(t1.transaction_date) AS period_end_date From quickbooks.credit_card_payment_txn t1

[fivetran-joemarkiewicz]

This is all great information, thanks so much @mikerenderco! Our team can scope out this enhancement to the package in our next sprint. Realistically I would imagine we could fold this into our package in October.

The code you shared though is fantastic and will really help us out. I would love for your to be credited for this contribution. If you would like to open a PR to even just add the csv file to our integration_tests/seeds/ folder we can credit your contribution 😄.

Regardless, we will plan to coordinate more here on any other questions we may have or any updates on our end. Thanks and I will keep you posted!

[lxuis97]

Hey @fivetran-joemarkiewicz,

What's the expected time to solve this issue?

Thanks!

[fivetran-joemarkiewicz]

Hi @lxuis97 you must have a sixth sense! I am actually exploring this as we speak. While I don't have a fix at the moment, I am working on the implementation outlined above. I will plan to keep you updated as I progress in this thread 😄

[lxuis97]

Haha great! Good to know 😊

[fivetran-joemarkiewicz]

HI @mikerenderco and @lxuis97 I have been able to get a working version of the package with the credit_card_payment_txn source baked into the General Ledger model (see the draft PR linked above if you want to see the details)! It would be great if you could give the branch a try and let me know if the implementation works on your data.

To test out the branch, you can use the following in your packages.yml:

packages:
  - git: https://github.com/fivetran/dbt_quickbooks_source.git
    revision: feature/credit-card-payments
    warn-unpinned: false

Once you add the contents to your packages.yml you can run dbt deps to install the new code and dbt run to generate your models. I look forward to hearing your feedback and if the added credit card payments fixes your issue!

[mikerenderco]

Hey Joe -

Sorry it took me so long to test this. I tested this but don't see anything with a transaction_source in the General_Ledger with a transaction_source of 'credit_card_payment'. I looked up specific Transaction_id's from the credit_card_payment_txn table in the GL but none of these transaction_id's exist. Am I missing something? select * From dbt_mlambeth_quickbooks.quickbooks__general_ledger where transaction_id = '29408'

[image: image.png]

On Tue, Sep 27, 2022 at 8:39 AM Joe Markiewicz @.***> wrote:

HI @mikerenderco https://github.com/mikerenderco and @lxuis97 https://github.com/lxuis97 I have been able to get a working version of the package with the credit_card_payment_txn source baked into the General Ledger model (see the draft PR linked above if you want to see the details)! It would be great if you could give the branch a try and let me know if the implementation works on your data.

To test out the branch, you can use the following in your packages.yml:

packages:

• git: https://github.com/fivetran/dbt_quickbooks_source.git revision: feature/credit-card-payments warn-unpinned: false

Once you add the contents to your packages.yml you can run dbt deps to install the new code and dbt run to generate your models. I look forward to hearing your feedback and if the added credit card payments fixes your issue!

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1259688605, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH6PXFWW646K63J7DALWAMIJZANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[fivetran-joemarkiewicz]

Hey @mikerenderco were you able to add the above packages.yml config to your project? If so, you will need to run dbt deps before running in order to see the updates.

[mikerenderco]

So i did do that this time! Let me try again though and just make sure.

On Wed, Oct 12, 2022 at 2:15 PM Joe Markiewicz @.***> wrote:

Hey @mikerenderco https://github.com/mikerenderco were you able to add the above packages.yml config to your project? If so, you will need to run dbt deps before running in order to see the updates.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1276744759, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTHYU3B2PUPEKCGYOU6DWC4S57ANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[mikerenderco]

So yes i was able to install the package: [image: image.png] then I ran it.

I then went in and ran a query on the specific transaction_id and its returning no data?

I may still be doing something wrong joe i'm not sure but its what i've done in the past.

SELECT * FROM allypediatrictherapy.dbt_mlambeth_quickbooks.quickbooks__general_ledger

where transaction_id = '29408'

On Wed, Oct 12, 2022 at 2:17 PM Mike Lambeth @.***> wrote:

So i did do that this time! Let me try again though and just make sure.

On Wed, Oct 12, 2022 at 2:15 PM Joe Markiewicz @.***> wrote:

Hey @mikerenderco https://github.com/mikerenderco were you able to add the above packages.yml config to your project? If so, you will need to run dbt deps before running in order to see the updates.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1276744759, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTHYU3B2PUPEKCGYOU6DWC4S57ANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

-- Mike Lambeth 775.813.0944 @.***

[fivetran-joemarkiewicz]

@mikerenderco my apologies, I forgot to mention that you will need to add a variable to your dbt_project.yml

vars:
    using_credit_card_payment_txn: true

We set it to false by default since only a number of customers leverage this table.

[mikerenderco]

Perfect so i reran it with that. I am now getting a few quickbooks_staging tables for the credit card transactions: [image: image.png]

But i still am not getting any of this data in the GL? select * From dbt_mlambeth_quickbooks.quickbooks__general_ledger where transaction_id = '29408' [image: image.png] I also looked by transaction source and don't see a Credit card transaction source in there.

On Thu, Oct 13, 2022 at 7:22 AM Joe Markiewicz @.***> wrote:

@mikerenderco https://github.com/mikerenderco my apologies, I forgot to mention that you will need to add a variable to your dbt_project.yml

vars: using_credit_card_payment_txn: true

We set it to false by default since only a number of customers leverage this table.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1277696278, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTHYCBYPD744Z43SLJSLWDALLPANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[fivetran-joemarkiewicz]

Thanks for the quick reply and looks like we are getting somewhere! Did you scope the variable above globally? You will need to make sure the variable is global or either listed under both quickbooks_source and quickbooks.

Are you able to see that transaction ID you are sharing in the staging table? Additionally, I am unable to see the images you are including in the messages 😢

[mikerenderco]

Hey Joe - Sorry about the images. I don't think i understand how to declare my variables globally. Let me try to post directly in Git.

1. I checkout the branch in development
2. I open the dbt_project.yml under the quickbooks_source folder
3. on the last line i paste your addition of using_credit_card_payment_txn: true
4. I then save the file
5. I then merge to main
6. I then dbt run
7. I don't see a folder titled quickbooks or a way to declare the variables globally
8. This is my unfamiliarity with dbt I think - if you can walk me through it i can test this.

[fivetran-joemarkiewicz]

Ahhhh you want to edit the variable in your root dbt_project.yml instead of the dbt_project.yml in the package.

Here is how I have it setup on my project:

[mikerenderco]

Ok Joe - I was able to get that in the global dbt_project. It runs successfully and moves the temp tables over for credit_card_payment_txn but I still don't see the records coming into the GL.

Here is my dbt_project.yml:

I tried matching my global dbt_project.yml exactly like yours but it won't compile. Says that there are errors.

[fivetran-joemarkiewicz]

Ah ha!! I think I see what the issue is. It looks like you are only installing the source package (as the snippet I sent above only is for the source package 🤦 , my apologies). Would you be able to try this snippet and see if you see the GL model updated?

packages:
  - git: https://github.com/fivetran/dbt_quickbooks.git
    revision: feature/credit-card-payments
    warn-unpinned: false

[mel-restori]

Hi @fivetran-joemarkiewicz ! I just started working with a team using Fivetran's dbt_quickbook integration and I'm investigating a credit card payment discrepancy. I'm diving into this thread and the PR you linked to. I'm new to Fivetran's dbt projects so apologies in advance if some of these questions are rather basic.

• First question - is that PR the latest place to look for updates on credit card payments?

• If so, I notice that stg_quickbooks__credit_card_payment_txn is never defined in dbt_project.yml. I assume it needs that definition to tie it to the raw table credit_card_payment_txn or is that defined elsewhere?

• Related, I'm confused by this line - I don't see the field is_most_recent_record in credit_card_payment_txn. Where can I see the logic that builds the field?

• Also, I haven't used dbt code as an imported package before so this question is pretty basic - if we set a variable in our dbt_project.yml (using_credit_card_payment_txn), will it overwrite the variable that is set in Fivetran's package dbt_project.yml? It doesn't matter in this case because you haven't declared that variable as far as I can tell in that PR, but I guess one day you will and the default will likely be false and we'll want in flipped to true.

Thank you!

[fivetran-joemarkiewicz]

Hi @mel-restori thanks for jumping into the thread! Hopefully I can help with some of your questions!

First question - is that PR the latest place to look for updates on credit card payments?

• Currently I would reference the feature/backwards-credit-card branch instead for the time being. At the moment we have a number of changes in flight (including this one) due to an upcoming dbt-utils v1.0.0 release that we are working on migration support within PR #51. However, we have noticed from this thread that users of the QuickBooks dbt package could benefit from these updates being rolled out prior to the migration updates. Therefore we are working on the branch highlighted above to possible merge before the migration updates later this month. In the packages.yml I would just reference the new branch for the time being if you wanted to try it out.

If so, I notice that stg_quickbooks__credit_card_payment_txn is never defined in dbt_project.yml. I assume it needs that definition to tie it to the raw table credit_card_payment_txn or is that defined elsewhere?

• It will be best practice for us to define the variable you mentioned in the dbt_project.yml. However, the current configuration should still work for the time being. But you are correct, and we will make sure to define the variable before official release.

Related, I'm confused by this line - I don't see the field is_most_recent_record in credit_card_payment_txn. Where can I see the logic that builds the field?

• This field is actually generated within the dbt_quickbooks_source package (which is a dependency defined within the packages.yml). This line in particular is generated here

Also, I haven't used dbt code as an imported package before so this question is pretty basic - if we set a variable in our dbt_project.yml (using_credit_card_payment_txn), will it overwrite the variable that is set in Fivetran's package dbt_project.yml? It doesn't matter in this case because you haven't declared that variable as far as I can tell in that PR, but I guess one day you will and the default will likely be false and we'll want in flipped to true.

• That is correct! The variables are created and defined so users are able to adjust the behavior of the package without needing to modify the code of the package directly. We will set the variable to false by default since the majority of users do not yet leverage this source table. However, since you do, you will be able to edit the variable in your own dbt_project.yml to change how the package functions.

Let me know if you have any other questions!

[mel-restori]

Hi Joe, thanks so much for all this! It's strange because stg_quickbooks__credit_card_payment_txn was never materialized, which makes me think maybe the variable wasn't set in the right spot. But I'll see about pointing to the new branch and rerunning to see if that helps resolve our cc payment issues. Thanks again!

[mel-restori]

Hi @fivetran-joemarkiewicz ! We went ahead and pointed to that other branch and finally see the credit card payments come through! 🎉 However, our discrepancy doubled in size 😭

It seems that the payments are coming through with the opposite signs. I think in the credit card accounts, the credit card payments should be positive, while in the bank account they should be negative. I think that's determined by debit vs credit in lines 36 and 50 here)., but I'll be honest that accounting terminology is new to me.

Does that sound right to you? Thanks again!

[fivetran-joemarkiewicz]

Hey @mel-restori that was actually something I was not entirely sure about when I added it to the branch and wanted to get confirmation on. I think you pointing this out is a great step forward in understanding the behavior of these transactions! I believe to fix this, we would just need to switch credit_card_account_id on line 35, with bank_account_id on line 59.

You have been really helpful in this process and if you wanted to contribute that quick switch in a PR, I would be happy to merge it into this working branch! Otherwise, I can make the update and we can see if this fix does the trick for you.

[fivetran-joemarkiewicz]

Thanks so much for opening the PR! I just approved and merged it into the working branch. Let me know if that reduces the discrepancy on your end. If not, we can switch back and continue investigating 😄

[mel-restori]

thank you!! hopefully that does it 🤞🏻. I'll update likely tomorrow.

[mikerenderco]

Hey @Joe Markiewicz @.***> - I know I had started testing this but i don't see CC payments in the GL. Was this ever pushed to prod or where you still waiting on some form of testing?

On Thu, Nov 10, 2022 at 3:22 PM Mel @.***> wrote:

thank you!! hopefully that does it 🤞🏻. I'll update likely tomorrow.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1311034279, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH6Q5EAAS2JZJSK7I3TWHV7R7ANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[fivetran-joemarkiewicz]

Hey @mikerenderco this has not been pushed to prod yet. We have this included in the migration PR #51 and were planning to officially release with those changes. However, that PR is waiting for the release of dbt-utils v1.0.0 (which has now been delayed a number of times).

As the release of dbt-utils v1.0.0 is taking longer than expected, we can prioritize releasing these updates before dbt Labs releases dbt-utils v1.0.0.

[mikerenderco]

Ok, thanks for the update. I am creating my own Creditcard payment records in the GL and its there are issues when new accounts are added. So would be good to see this release in prod.

On Mon, Dec 5, 2022 at 11:36 AM Joe Markiewicz @.***> wrote:

Hey @mikerenderco https://github.com/mikerenderco this has not been pushed to prod yet. We have this included in the migration PR #51 https://github.com/fivetran/dbt_quickbooks/pull/51 and were planning to officially release with those changes. However, that PR is waiting for the release of dbt-utils v1.0.0 (which has now been delayed a number of times).

As the release of dbt-utils v1.0.0 is taking longer than expected, we can prioritize releasing these updates before dbt Labs releases dbt-utils v1.0.0.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1338044735, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH6NNFNUWWY7WJ73PUTWLY74DANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[fivetran-joemarkiewicz]

Sure thing @mikerenderco! I just opened the PR above to merge these changes in before the migration changes.

Before doing so, would you be able to give the changes a test and confirm all looks good on your end?

packages:
  - git: https://github.com/fivetran/dbt_quickbooks.git
    revision: feature/backwards-credit-card
    warn-unpinned: false

[mikerenderco]

Joe - I tried to test this but everything runs and I don't ever get Credit_Card_Payment_txn records in to the GL. Not sure what i'm doing wrong.

On Mon, Dec 5, 2022 at 2:22 PM Joe Markiewicz @.***> wrote:

Sure thing @mikerenderco https://github.com/mikerenderco! I just opened the PR above to merge these changes in before the migration changes.

Before doing so, would you be able to give the changes a test and confirm all looks good on your end?

packages:

• git: https://github.com/fivetran/dbt_quickbooks.git revision: feature/backwards-credit-card warn-unpinned: false

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1338262754, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH3CB4P3EXAXTQCYYDDWLZTMBANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

[mel-restori]

@mikerenderco I was troubleshooting this myself a couple weeks ago and seems to work for me now. Note that the branch Joe pointed you to today is different than the branch you were working off of in October, so maybe that's what's still causing issues for you? 🤷🏻‍♀️ Good luck!

[fivetran-joemarkiewicz]

Thanks for confirming @mel-restori and that is great to hear that it worked on your end!

@mikerenderco, @mel-restori is correct in pointing out that the branch has changed. Would you be able to use the following in your packages.yml and try again?

packages:
  - git: https://github.com/fivetran/dbt_quickbooks.git
    revision: feature/backwards-credit-card
    warn-unpinned: false

[mikerenderco]

@Joe Markiewicz @.***> super confused. I just ran the above package and I'm still not getting any CC_payment records in our General Ledger in Bigquery. I have attached my logs for dbt deps and dbt run.

I tried to run this query and I'm getting no results:

select * From dbt_mlambeth_quickbooks.quickbooks__general_ledger where transaction_id = '24211'

transaction 24w11 is a credit_card_payment_txn transaction.

On Mon, Dec 5, 2022 at 8:16 PM Joe Markiewicz @.***> wrote:

Thanks for confirming @mel-restori https://github.com/mel-restori and that is great to hear that it worked on your end!

@mikerenderco https://github.com/mikerenderco, @mel-restori https://github.com/mel-restori is correct in pointing out that the branch has changed. Would you be able to use the following in your packages.yml and try again?

packages:

• git: https://github.com/fivetran/dbt_quickbooks.git revision: feature/backwards-credit-card warn-unpinned: false

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1338722573, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH277GMT4RHPW7Y5L3LWL242BANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

18:01:43 Unable to do partial parsing because config vars, config profile, or config target have changed 18:01:48 [WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources. There are 1 unused configuration paths:

• models.my_new_project.example

18:01:49 Found 107 models, 57 tests, 0 snapshots, 2 analyses, 640 macros, 0 operations, 0 seed files, 40 sources, 0 exposures, 0 metrics 18:01:49
18:01:49 Concurrency: 4 threads (target='default') 18:01:49
18:01:49 1 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksaccount_tmp [RUN] 18:01:49 2 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__address_tmp [RUN] 18:01:49 3 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_line_tmp [RUN] 18:01:49 4 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_linked_txn_tmp [RUN] 18:01:50 4 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__bill_linked_txn_tmp [OK in 0.89s] 18:01:50 5 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_line_tmp [RUN] 18:01:50 3 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_line_tmp [OK in 0.90s] 18:01:50 6 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_tmp [RUN] 18:01:50 2 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksaddress_tmp [OK in 0.91s] 18:01:50 7 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__bill_tmp [RUN] 18:01:50 1 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksaccount_tmp [OK in 0.93s] 18:01:50 8 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_item_tmp [RUN] 18:01:51 5 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_line_tmp [OK in 0.77s] 18:01:51 9 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_tmp [RUN] 18:01:51 7 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__bill_tmp [OK in 0.76s] 18:01:51 10 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_line_tmp [RUN] 18:01:51 6 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_tmp [OK in 0.78s] 18:01:51 11 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_tmp [RUN] 18:01:51 8 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_item_tmp [OK in 0.78s] 18:01:51 12 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookscustomer_tmp [RUN] 18:01:51 10 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_line_tmp [OK in 0.52s] 18:01:51 13 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__department_tmp [RUN] 18:01:52 9 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_tmp [OK in 0.78s] 18:01:52 14 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit_line_tmp [RUN] 18:01:52 11 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_tmp [OK in 0.76s] 18:01:52 15 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit_tmp [RUN] 18:01:52 12 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__customer_tmp [OK in 0.76s] 18:01:52 16 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate_line_tmp [RUN] 18:01:52 15 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit_tmp [OK in 0.77s] 18:01:52 17 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__estimate_tmp [RUN] 18:01:52 14 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit_line_tmp [OK in 0.79s] 18:01:52 18 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_bundle_tmp [RUN] 18:01:52 16 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate_line_tmp [OK in 0.89s] 18:01:52 19 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_tmp [RUN] 18:01:53 13 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__department_tmp [OK in 1.63s] 18:01:53 20 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_linked_txn_tmp [RUN] 18:01:53 18 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_bundle_tmp [OK in 0.75s] 18:01:53 21 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__invoice_tmp [RUN] 18:01:53 17 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate_tmp [OK in 0.78s] 18:01:53 22 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksitem_tmp [RUN] 18:01:53 19 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_tmp [OK in 0.79s] 18:01:53 23 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry_line_tmp [RUN] 18:01:54 20 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_linked_txn_tmp [OK in 0.63s] 18:01:54 24 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry_tmp [RUN] 18:01:54 21 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_tmp [OK in 0.74s] 18:01:54 25 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_line_tmp [RUN] 18:01:54 22 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksitem_tmp [OK in 0.76s] 18:01:54 26 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_tmp [RUN] 18:01:54 23 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__journal_entry_line_tmp [OK in 0.89s] 18:01:54 27 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_line_tmp [RUN] 18:01:54 24 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry_tmp [OK in 0.76s] 18:01:54 28 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_tmp [RUN] 18:01:55 26 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_tmp [OK in 0.73s] 18:01:55 29 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__refund_receipt_line_tmp [RUN] 18:01:55 25 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_line_tmp [OK in 0.78s] 18:01:55 30 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt_tmp [RUN] 18:01:55 28 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_tmp [OK in 0.51s] 18:01:55 31 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt_line_tmp [RUN] 18:01:55 27 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_line_tmp [OK in 0.72s] 18:01:55 32 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt_tmp [RUN] 18:01:55 30 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt_tmp [OK in 0.67s] 18:01:55 33 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbookstransfer_tmp [RUN] 18:01:55 29 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt_line_tmp [OK in 0.79s] 18:01:55 34 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_line_tmp [RUN] 18:01:56 31 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooks__sales_receipt_line_tmp [OK in 0.76s] 18:01:56 35 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_tmp [RUN] 18:01:56 32 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt_tmp [OK in 0.76s] 18:01:56 36 of 78 START view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_tmp [RUN] 18:01:56 33 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbookstransfer_tmp [OK in 0.75s] 18:01:56 37 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_linked_txn [RUN] 18:01:56 34 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_line_tmp [OK in 0.74s] 18:01:56 38 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksaddress [RUN] 18:01:56 36 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_tmp [OK in 0.75s] 18:01:56 39 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__bill_line [RUN] 18:01:57 35 of 78 OK created view model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_tmp [OK in 0.89s] 18:01:57 40 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksaccount [RUN] 18:01:58 37 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_linked_txn [CREATE TABLE (3.0k rows, 64.2 KB processed) in 2.34s] 18:01:58 41 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_line [RUN] 18:01:59 38 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksaddress [CREATE TABLE (112.0 rows, 5.0 KB processed) in 2.64s] 18:01:59 42 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill [RUN] 18:01:59 40 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksaccount [CREATE TABLE (291.0 rows, 44.4 KB processed) in 2.58s] 18:01:59 43 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment [RUN] 18:01:59 39 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__bill_line [CREATE TABLE (3.4k rows, 270.7 KB processed) in 2.91s] 18:01:59 44 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_item [RUN] 18:02:01 41 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment_line [CREATE TABLE (3.1k rows, 90.3 KB processed) in 2.51s] 18:02:01 45 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_line [RUN] 18:02:02 43 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill_payment [CREATE TABLE (3.0k rows, 152.8 KB processed) in 2.65s] 18:02:02 46 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle [RUN] 18:02:02 44 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle_item [CREATE TABLE (0.0 rows, 0 processed) in 2.56s] 18:02:02 47 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo [RUN] 18:02:03 42 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbill [CREATE TABLE (3.1k rows, 211.0 KB processed) in 4.53s] 18:02:03 48 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookscustomer [RUN] 18:02:04 45 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo_line [CREATE TABLE (0.0 rows, 0 processed) in 2.62s] 18:02:04 49 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit [RUN] 18:02:04 47 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookscredit_memo [CREATE TABLE (0.0 rows, 0 processed) in 2.32s] 18:02:04 50 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__deposit_line [RUN] 18:02:05 46 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksbundle [CREATE TABLE (0.0 rows, 0 processed) in 2.87s] 18:02:05 51 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate_line [RUN] 18:02:06 48 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookscustomer [CREATE TABLE (31.0 rows, 1.9 KB processed) in 2.29s] 18:02:06 52 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksdepartment [RUN] 18:02:06 49 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksdeposit [CREATE TABLE (9.6k rows, 388.3 KB processed) in 2.29s] 18:02:06 53 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_bundle [RUN] 18:02:07 50 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__deposit_line [CREATE TABLE (9.8k rows, 879.1 KB processed) in 2.57s] 18:02:07 54 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate [RUN] 18:02:07 51 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate_line [CREATE TABLE (0.0 rows, 0 processed) in 2.63s] 18:02:07 55 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__invoice_line [RUN] 18:02:08 53 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_line_bundle [CREATE TABLE (0.0 rows, 0 processed) in 2.35s] 18:02:08 56 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_linked_txn [RUN] 18:02:08 52 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksdepartment [CREATE TABLE (11.0 rows, 823.0 Bytes processed) in 2.60s] 18:02:08 57 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice [RUN] 18:02:09 54 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksestimate [CREATE TABLE (0.0 rows, 0 processed) in 2.44s] 18:02:09 58 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksitem [RUN] 18:02:11 56 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice_linked_txn [CREATE TABLE (13.0 rows, 246.0 Bytes processed) in 2.86s] 18:02:11 59 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry_line [RUN] 18:02:11 57 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksinvoice [CREATE TABLE (13.0 rows, 786.0 Bytes processed) in 2.90s] 18:02:11 60 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry [RUN] 18:02:11 55 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__invoice_line [CREATE TABLE (61.0 rows, 3.5 KB processed) in 4.03s] 18:02:11 61 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment [RUN] 18:02:12 58 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksitem [CREATE TABLE (18.0 rows, 1.0 KB processed) in 2.32s] 18:02:12 62 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_line [RUN] 18:02:13 60 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry [CREATE TABLE (991.0 rows, 76.8 KB processed) in 2.23s] 18:02:14 61 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment [CREATE TABLE (15.0 rows, 635.0 Bytes processed) in 2.25s] 18:02:14 64 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_line [RUN] 18:02:14 63 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase [RUN] 18:02:14 59 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksjournal_entry_line [CREATE TABLE (71.3k rows, 5.8 MB processed) in 2.82s] 18:02:14 65 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt [RUN] 18:02:14 62 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookspayment_line [CREATE TABLE (14.0 rows, 380.0 Bytes processed) in 2.49s] 18:02:14 66 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt_line [RUN] 18:02:16 65 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt [CREATE TABLE (0.0 rows, 0 processed) in 2.42s] 18:02:16 67 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt_line [RUN] 18:02:16 66 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksrefund_receipt_line [CREATE TABLE (0.0 rows, 0 processed) in 2.31s] 18:02:16 68 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt [RUN] 18:02:16 63 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase [CREATE TABLE (11.6k rows, 680.3 KB processed) in 2.76s] 18:02:16 69 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbookstransfer [RUN] 18:02:16 64 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookspurchase_line [CREATE TABLE (12.7k rows, 2.3 MB processed) in 2.90s] 18:02:16 70 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_line [RUN] 18:02:19 67 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt_line [CREATE TABLE (2.0 rows, 70.0 Bytes processed) in 2.20s] 18:02:19 71 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor [RUN] 18:02:19 69 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookstransfer [CREATE TABLE (382.0 rows, 12.1 KB processed) in 2.22s] 18:02:19 72 of 78 START table model dbt_mlambeth_quickbooks_staging.stg_quickbooks__vendor_credit [RUN] 18:02:19 68 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbookssales_receipt [CREATE TABLE (1.0 rows, 55.0 Bytes processed) in 2.30s] 18:02:19 70 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit_line [CREATE TABLE (39.0 rows, 3.1 KB processed) in 2.29s] 18:02:21 71 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor [CREATE TABLE (512.0 rows, 26.8 KB processed) in 2.35s] 18:02:21 73 of 78 START table model dbt_mlambeth_quickbooks.quickbooksap_ar_enhanced .. [RUN] 18:02:22 72 of 78 OK created table model dbt_mlambeth_quickbooks_staging.stg_quickbooksvendor_credit [CREATE TABLE (32.0 rows, 2.3 KB processed) in 3.10s] 18:02:22 74 of 78 START table model dbt_mlambeth_quickbooks.quickbooksgeneral_ledger .. [RUN] 18:02:22 75 of 78 START table model dbt_mlambeth_quickbooks.quickbooksexpenses_sales_enhanced [RUN] 18:02:24 73 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooksap_ar_enhanced [CREATE TABLE (3.1k rows, 315.6 KB processed) in 3.44s] 18:02:26 75 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooksexpenses_sales_enhanced [CREATE TABLE (37.2k rows, 9.8 MB processed) in 4.34s] 18:02:29 74 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooksgeneral_ledger [CREATE TABLE (128.9k rows, 3.8 MB processed) in 7.22s] 18:02:33 76 of 78 START table model dbt_mlambeth_quickbooks.quickbooksgeneral_ledger_by_period [RUN] 18:02:37 76 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooksgeneral_ledger_by_period [CREATE TABLE (22.1k rows, 16.9 MB processed) in 4.51s] 18:02:37 77 of 78 START table model dbt_mlambeth_quickbooks.quickbooks__balance_sheet ... [RUN] 18:02:37 78 of 78 START table model dbt_mlambeth_quickbooks.quickbooksprofit_and_loss . [RUN] 18:02:40 77 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooks__balance_sheet [CREATE TABLE (12.1k rows, 2.9 MB processed) in 2.41s] 18:02:40 78 of 78 OK created table model dbt_mlambeth_quickbooks.quickbooks__profit_and_loss [CREATE TABLE (10.0k rows, 2.9 MB processed) in 2.46s] 18:02:40
18:02:40 Finished running 36 view models, 42 table models in 0 hours 0 minutes and 51.35 seconds (51.35s). 18:02:40
18:02:40 Completed successfully 18:02:40
18:02:40 Done. PASS=78 WARN=0 ERROR=0 SKIP=0 TOTAL=78 17:59:39 Installing https://github.com/fivetran/dbt_quickbooks.git 17:59:43 Installed from revision feature/backwards-credit-card 17:59:43 Installing https://github.com/fivetran/dbt_quickbooks_source.git 17:59:47 Installed from revision feature/backwards-credit-card 17:59:47 Installing fivetran/fivetran_utils 17:59:48 Installed from version 0.3.9 17:59:48 Updated version available: 0.4.0 17:59:48 Installing dbt-labs/dbt_utils 17:59:53 Installed from version 0.8.6 17:59:53 Updated version available: 1.0.0 17:59:53
17:59:53 Updates available for packages: ['fivetran/fivetran_utils', 'dbt-labs/dbt_utils']
Update your versions in packages.yml, then run dbt deps

[mikerenderco]

@Joe Markiewicz @.***> please ignore last response. I am now seeing the credit_card_payment_txn in the General Ledger. We can confirm that the correct items are being posted. Can you get this pushed live? Also when you do please let me know so I can stop creating unions for these myself.

This is fantastic.

On Mon, Dec 12, 2022 at 10:10 AM Mike Lambeth @.***> wrote:

@Joe Markiewicz @.***> super confused. I just ran the above package and I'm still not getting any CC_payment records in our General Ledger in Bigquery. I have attached my logs for dbt deps and dbt run.

I tried to run this query and I'm getting no results:

select * From dbt_mlambeth_quickbooks.quickbooks__general_ledger where transaction_id = '24211'

transaction 24w11 is a credit_card_payment_txn transaction.

On Mon, Dec 5, 2022 at 8:16 PM Joe Markiewicz @.***> wrote:

Thanks for confirming @mel-restori https://github.com/mel-restori and that is great to hear that it worked on your end!

@mikerenderco https://github.com/mikerenderco, @mel-restori https://github.com/mel-restori is correct in pointing out that the branch has changed. Would you be able to use the following in your packages.yml and try again?

packages:

• git: https://github.com/fivetran/dbt_quickbooks.git revision: feature/backwards-credit-card warn-unpinned: false

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#issuecomment-1338722573, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH277GMT4RHPW7Y5L3LWL242BANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***

-- Mike Lambeth 775.813.0944 @.***

Compilation Error in model int_quickbookscredit_card_pymt_double_entry (models/double_entry_transactions/int_quickbooks__credit_card_pymt_double_entry.sql) Model 'model.quickbooks.int_quickbookscredit_card_pymt_double_entry' (models/double_entry_transactions/int_quickbooks__credit_card_pymt_double_entry.sql) depends on a node named 'stg_quickbooks__credit_card_payment_txn' which is disabled

[fivetran-joemarkiewicz]

Hey all, this should be live now in v0.5.4!!

[mel-restori]

awesome, thank you!!

[fivetran-joemarkiewicz]

Closing this ticket as the updates are now live. Thanks @mel-restori and @mikerenderco for all your help in getting these updates tested and raising the initial issue to our team 😃

[mikerenderco]

Thanks Joe! - One question that i've been trying to figure out. I am using DBT Cloud. On all DBT cloud production jobs they run a DBT deps. How do i maintain the change to using using_credit_card_payment_txn: true?

Because it goes out and runs a DBT DEPS before a DBT RUN my var always gets reset to false in the dbt_project.yml under the quickbooks model and the quickbooks_source model.

On Tue, Dec 13, 2022 at 11:19 AM Joe Markiewicz @.***> wrote:

Closed #47 https://github.com/fivetran/dbt_quickbooks/issues/47 as completed.

— Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_quickbooks/issues/47#event-8029472532, or unsubscribe https://github.com/notifications/unsubscribe-auth/A23MTH2INI2UILQVTBJA4KLWNDD5RANCNFSM6AAAAAAQRJAQUE . You are receiving this because you were mentioned.Message ID: @.***>

-- Mike Lambeth 775.813.0944 @.***