Power Query - cache shared nodes
Update Power Query in Excel to take advantage of caching in cases where a parent node refers to a child node that has already been refreshed (as exists in Power BI desktop today).
This issue creates significant performance problems with refresh times when creating highly interdependent financial and operational models. This is a show stopper from a usability and customer acceptance standpoint.
We are happy to announce that the feature is finally available on Production starting from July fork (build 16.0.10726.*) for Office 365 subscribers.
Thank you all for your votes and the feedback.
- Excel Team
Tim Thurnham commented
PowerQuery still suffers from terrible refresh speeds. Both when actually running the query, and, most infuriatingly, during editing.
This turns a good product into a bad one.
Please, please fix this properly.
I still have this in Excel o365 where it refreshes all queries even although referenced - has this been tested ?
Add to non 365 users! Now please!
Scott Bonczkowski commented
I am still experiencing slow refresh rates in Excel 2016.
Annette Clark commented
How about Excel 2016??? I am having serious issues!
Is this resolve now for Excel 2016?
I am facing with slow refresh.
but.... what about us on Excel 2016??
Hi. What about on premise 2016?
Refreshing a queray and then saving it takes a long time! real;y frustrating!
the connection from an excel Power Query to a data source in another Excel workbook need to much time.
just stop using Power query. Use R.
Their is really 0 reason to fiddle around with DAX / Power query any more - this was an interesting idea but MS really did not give it enough juice to get it in the air and make it compete with the much better options already around.
Seriously if you can code something in the mess that is DAX learn R or python. It is just better.
Other languages are easier to code and do more.
If it's marked Completed then they are no longer working this issue. The irony about this is that if you manually make a DAO connection to a DB and run queries in VBA it's lighting fast! Their new method is vastly slower and more inefficient than the old way of pulling data from a DB. So write your own methods. I'm sure you can write something that is faster before Microsoft can.
What are the means of escalating issues?
Bruno Crotman commented
No one listens.... Give up! I gave up. Use R!
Rich S commented
Do we even know if Microsoft is even looking at this anymore since it's been marked [Completed] which is complete BS.
By the way, a workaround that has worked for me if it's available to you is to use Excel 2010 and I think Excel 2013 works too. Those versions don't have the painful Power Query refresh issues that exist in Excel 2016. While you can't have 2013 and 2016 installed on the same machine you can have 2010 and 2016 so when I can't get something to run on 2016 I open up 2010 and run it there. Hate to have to do it but it seems to work pretty well for me.
Came across a thread related to query refresh times, and came here to also comment...it is SLOW. Running 2016 Pro Plus, 64-bit, Windows 10.
Rich S commented
Agreed. We jumped on the Power Query bandwagon when it first came out and loved it but now am having to consider switching away a number of our processes away from Power Query. It feels like a complete waste of time to have to do so but what can you do when Microsoft does not address a problem that obviously affects many us.
@Abdur. I can definitely relate to your pain.
Abdur Mohid commented
I just want to say that I was a massive fan of Power Query when I first discovered it. However Microsoft seems to have neglected this kit for so long with the refresh times, it is no longer usable in any capacity for my work.
I can easily spend 80-90% of my working day just waiting for it to load!
In summary, if you value your time and life DO NOT USE POWER QUERY UNDER ANY CIRCUMSTANCES!!
IT IS RUBBISH AND DISGRACEFUL FROM MICROSOFT
Bruno Crotman commented
Yes. The light is R and Tidyverse