Forum Discussion
PBIX error on refresh - but no Errors in Query Error Table
- Anonymous3 years ago
Hi Everyone
The solution I have found, which seems to work for me, is to make the Source SharePoint address a Parameter:This can then be mnaged separately to the list of queries linked to it
I can then have my Table of Files, with Date Modified, "without" the Binary Column (which seemed to be the source of the errors, even though Power BI didnt really know what the error was)
Getting data from files on Sharepoint is difficult, comlex, and subject to bugs, which is why we minimize the files we store on Sharepoint. Avoiding files on Sharepoint is an important consideration for our design process. However you can try some of these steps:
Process 1
- Open you PBIX file in PBI Desktop that connects to files on Sharepoint.
- Log off power BI. In the upper left of the PBI window click your name, then log out.
- Close the PBIX file.
- Open the PBIX file.
- Log in to PBI Desktop again.
- Try to do your refresh.
If that doesn't work try these steps.
Process 2
Go to app.powerbi.com. Sign in using your username.
Find the data portion. Click the 3 dots, then settings.
Go to Data Source Credentials area.
I think you can sign out of the Sharepoint Datasource. Then sign back in. I don't have access to Data Source Credentials but try that.
Process 3
Go to the sharepoint site in your browser. Sign out of the site. Sign back in.
Hi Again
Sadly no improvement. I have signed out, shut down, rebooted, signed in and re-refreshed as many ways as I can and I still have problems - new ones now...
I could not faff with Credentials via app.powerbi.com as I have not yet published this report - that will wait till I am ready to roll it out
- Anonymous3 years agoNot applicable
Hi Everyone
The solution I have found, which seems to work for me, is to make the Source SharePoint address a Parameter:This can then be mnaged separately to the list of queries linked to it
I can then have my Table of Files, with Date Modified, "without" the Binary Column (which seemed to be the source of the errors, even though Power BI didnt really know what the error was)