How To Get QuickBooks Exports into Excel with Power Query | Excel Formula Hacks

[@meetprajapati7956]

Love it Please make more video on report automation for qbo

[@dmitripopov8570]

Brilliant! Thank you. It makes it quite clear that there is no proper batch conversion at this point. Uuuff...

[@JoyEll]

Excellent video, this will help me out a lot. Thank you Jeff!

[@mhaft]

Thanks for showing the PQ steps. Is there a way for this to be useful in Pivot tables? There is no much duplication and the row labels are in alphabetical order instead of Income Statement order.

[@ExcelU]

I show how to use power query to clean the data, and then how to use a pivot table to create a balance sheet here: kzbin.info/www/bejne/gKuaZKqIqt6IqcU I hope this can be helpful :) Thanks Jeff

[@mhaft]

@@ExcelU Thanks Jeff for the response. I'll check it out.

[@twarren3685]

Very helpful. I was trying to avoid opening the Excel file before loading into Power query by downloading the data in pdf format from QB, but found the monthly data was not always in the same columns when loading and transforming.

[@ExcelU]

Glad it helped!

[@neenabentley5875]

I love this!!!!

[@ExcelU]

Thank you :)

[@LMDFAITH]

I am trying to use this to export my item list from QB. Added columns for desired margin and suggested sales price. But everytime I refresh with updated costs it wipes my formula columns at the end. How can I keep these 4 formula columns put and just have the data from QB updated?

[@josealvesferreira1683]

very very good

[@ExcelU]

Many many thanks

[@Jimo_M]

Hey Jeff, thanks for showing us this quick hack. Quick question, after I’ve saved a new updated file in the same folder and with the same file name as the original file I transformed, when I click refresh, I get the following error message “[Expression.Error] The column ‘Apr 1, 2023’ of the table wasn’t found”. For context the original file I transformed had Apr 2023 as the last month and the new update file I’m running has the latest month as May 1, 2023. What am I doing wrong?

[@oliverantoniou]

You probably have a step in Power Query that specifically refers to that column name. Maybe a Changed Type step which can be deleted