Forum Discussion
Power Query SharePoint Connections Refresh Speeds
Hi, the best approach would be use filtering in the Source step or as early as possible to avoid loading full content of lists if you're only interested in metadata like item count, permissions, or last modified date.
There's official Microsoft documentation recommending filtering as early as possible in Power Query. This means placing your Table.SelectRows(...) filters immediately after the data source step so that fewer rows are pulled into Power BI, reducing memory and processing time.
Best practices when working with Power Query - Power Query | Microsoft Learn
I am using the sharepoint.file quite a bit on a 10K file + sharepoint site.
Yes, it takes some time and filtering early does not seem to make any difference.
You can try your luck with Sharepoint.Contents(). It is much faster, but does not return thhe same data and returns it in a different format. I also expereinced som unexplicable errors at some point, but that is 2 years ago and may be resolved now...
Did I answer your question? Then please (also) mark my post as a solution and make it easier to find for others having a similar problem.
Remember: You can mark multiple answers as a solution...
If I helped you, please click on the Thumbs Up to give Kudos.
Kees Stolker
A big fan of Power Query and Excel
Let me clearify my problem now. And I use the function SharePoint.Contents in the following file.
After June, the same file in the Desktop PQ refreshes very slow(may not success) and the memory goes up very high then the program doesn't respond. At the same time, I open another file(the old version) works. So I think it's not the problem of the network.
I turn to suspect maybe this file goes error. But another day this file can work in the PQ refreshing. So I am not sure what happens. The file today refreshes successfully, another day fails. What goes wrong after all? I don't know.
