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.

Hi all,
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
310 comments
-
Anonymous commented
Top priority please
-
Lenny W. commented
Kindly fix the PQ slow refreshing issue.
Lenny -
Jes Hansen commented
Power Query + Power pivot in Excel = Great show starter
Slow refreshing in PQ + crashing in PP = Bad show stopperCustomers are actively rejecting the PQ + PP combination because of this and since some investment has already been allocated in the process before realizing the facts some badwill is returned towards Micorsoft and the consultants involved. A sound ROI would be much better for all those involved. PLEASE FIX THIS
-
Dan commented
PQ is an amazing tool and has revolutionised financial modelling within our organisation. However, we have had to stop using PQ solutions due to the refresh speed. This needs to be fixed urgently.
-
Tommy Jørgensen commented
Important fix
-
Anonymous commented
Biggest issue with Power Query. #1 priority.
-
Anonymous commented
Top priority. Slow refresh times are a big problem.
-
Simon commented
This should be ranked #1 above all other priorities. The performance is so terrible that it should almost be considered a bug.
-
Anonymous commented
Having to sit and wait for 10 minutes for a Power Query refresh is a drag (when it's just re-querying the same data repeatedly)! Please fix.
-
Dylan commented
Can we get an update on this?
-
Dick commented
Needs to be fixed!
-
Will Golay commented
Please keep high on priority list. It can take anywhere from 30-90 seconds to refresh a total of 100 rows separated into 15ish tables, far too long to be worth updating from the old legacy wizards for imports to the new OLE DB query connections.
-
UK_GER commented
Pls. help us. Not all users have access to all Software (Power BI) in their companies.
But still we spend hours because PQ is "like a drug".
Decision makers from IT just wait to see us fail with "the toy" - and the door to P-BI starts to close before it opens.UK_GER
-
Anonymous commented
I agree
-
Anonymous commented
need to be fixed!
-
Anonymous commented
Upvote!
-
linda commented
I agree
-
Imke Feldmann commented
For recursive operations like an explosion of a Bill of materials table the performance difference between Power Query in Excel and PowerBI is vast: http://wp.me/p6lgsG-wV . Very hard to see what's possible in PowerBI with the same code that hopelessly fails in Excel. Please give us the power here as well!
-
ab commented
I agree
-
Anonymous commented
I agree