Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi there,
Recently i've been having this error a lot of times which makes it almost impossible to refresh my data:
I've been researching here for similar problems but i just can't fix it. I've tried to edit credentials, reset them and log on again and it still gives me this error.
My data sources are SharePoint folders and excel files.
I want to understand what is causing this and a possible solution.
Thank you
Solved! Go to Solution.
So to answer to both of @009co and @Daryl-Lynch-Bzy , in my M Query i had a parameter where the user would choose which SharePoint folder powerbi would import data from. Today was the first time i was able to refresh data (i deleted some tables and relationships) and it turns out it was importing 20 MILLION rows (and counting). So i deleted the parameter and put the path by hand, like i always do, on the navigation step and it worked perfectly after. I assumed it was because of the parameter but never would've thought it was pulling all the files from my O365 Team. This most likely caused A LOT of calls to SharePoint and thus the error.
Thank you both
Edit: it was actually pulling more than 100M rows, so clearly this could've triggered something.
I found a bypass. Try the solution at: Using the wait-retry pattern in Power Query connectors - Power Query | Microsoft Docs
So to answer to both of @009co and @Daryl-Lynch-Bzy , in my M Query i had a parameter where the user would choose which SharePoint folder powerbi would import data from. Today was the first time i was able to refresh data (i deleted some tables and relationships) and it turns out it was importing 20 MILLION rows (and counting). So i deleted the parameter and put the path by hand, like i always do, on the navigation step and it worked perfectly after. I assumed it was because of the parameter but never would've thought it was pulling all the files from my O365 Team. This most likely caused A LOT of calls to SharePoint and thus the error.
Thank you both
Edit: it was actually pulling more than 100M rows, so clearly this could've triggered something.
That is an impressively large number of records!
Interesting, I am also using a parameter for the SharePoint url.
I am using a parameter for the folder because I was doing dev on local machine and dataset, and testing on different SharePoint sites. It was easier to change parameter value than updating url manually in a bunch of queries and functions.
However, my parameter is hardcoded eg doesn't require anyone to choose it. But will try hardcoding the url and see what happens.
Although this still doesn't explain why it works most of the time, but randomly fails.
This is happening for me too.
Hi @Anonymous - could you please share the advanced editor (M Query) steps. Please replace the URL ("xxx") without hiding all the detail. My thinking is that you are using the wrong path in the SharePoint function you are using.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.