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
Definitely support this request
Would love this issue resolved
Imke Feldmann commented
I suspect there is more to the performance problems than shared nodes, but this would definitely be a good start! Full support from me.
It is really a big issue. I have queries in my company which i have to start over night because of the time consumption...
Chris Higgins commented
Agreed all around with refresh times. Could be internal server issues, but filtering and sorting when dealing with greater than 50K+ rows results in significant latency. In regards to display, when creating pivot tables, a more user friendly interface would be great when filtering between stacked pivot options (possible dropdown option on face of pivot). I would love to see an enhanced ability for excel to identify chronologies in pivot tables, i.e. when utilizing dates as headers, 1/15 would always be listed before 1/2. This would simply reduce the need for manual manipulation by users.
Slow refreshing sucks
I love Power Query.
My Power Query routines are getting more complex and handling larger data sets.
It would be very helpful to have faster query response time.
Anthony McRae commented
Consider my vote is done Ken.
Wyn Hopkins commented
Power Query is blowing users minds when they see it in action, refresh speed in Excel however can be unacceptably slow. Any improvements in this area would be greatly welcomed.