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
Please please please. I have lots of reports I need Power Query to feed and they just are feasible because they are dreadfully slow to upload.
Justin Mannhardt commented
Agreed, much needed. Seconds matter, priority up!
using work around because of speed, amazing tool but users feel frustrated when they have to walk away and wait for querys to cycle.
Gerald Hinrichs commented
This is a "gotta have".
"One small step for man" - what else can we all say/do to encourage you guys?
Imke Feldmann commented
Dear Excel Team,
as far as I can see, this issue is on 3rd rank in Excel for Windows and on 7th rank in Excel over all. Wondering how much more we need to overcome the priority-threshold here?
Thx - Imke
Please fix PowerQuery refresh latency issues, thank you
This is my biggest challenge using PQ and an impediment to getting others in my organization on the PQ bandwagon. Please fix.
Top priority please
Lenny W. commented
Kindly fix the PQ slow refreshing issue.
Jes Hansen commented
Power Query + Power pivot in Excel = Great show starter
Slow refreshing in PQ + crashing in PP = Bad show stopper
Customers 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
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
Biggest issue with Power Query. #1 priority.
Top priority. Slow refresh times are a big problem.
This should be ranked #1 above all other priorities. The performance is so terrible that it should almost be considered a bug.
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.
Can we get an update on this?
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.