Forum Discussion
Cannot open report using shared dataset 11-12-2020
Update: I was finally able to trigger the 'Select Dataset' Dialogue to open by launching power BI without a report, then opening the report with a shared dataset from the side. The same error appears, but now retry opens the dialogue.
Once I went through this process and saved the report, I could launch it from file explorer normally. This is 100% a work around though. Does anyone have insight into what might have caused this? Reports with built in datasets are not acting this way.
Additional Info: these same reports are now blank in Power BI Pipelines. The prod workspace is fine, but both dev and test completely fail to render their copies of these reports.
HI Anonymous,
It seems like you are working with a report that 'live connection' to the shared dataset, right? If this is a case, have you test with multiple credentials in your report?
AFAIK, current power bi will cache the credentials into the local and it not support using multiple credentials with the same Datasource types. (new credentials will replace the previous one and the data source tables who use the old credentials will be failed to load)
In addition, can you please share more detailed information about your operations?
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
Thanks for checking in!
I am using a report with a 'Live connection' to a power BI Shared dataset.
There are not Multiple credentials.
What details would be beneficial?
Hi Anonymous,
Currently. power bi desktop uses the signed-in account as the credentials to link live mode power bi dataset.
If you switch the signed-in account or removed the corresponding dataset permissions from the current account, it will show the message as your snapshot displayed.Regards,
Xiaoxin Sheng
That's the thing, I didn't do either of those things. The reports (All shared reports on multiple datasets across multiple workspaces) show that dialogue, then fail to open the 'Select a dataset to create a report dialogue'. Instead they either show a 'Script Error' or disappear, locking up power bI desktop. The only exception is the workaround I posted, after doing that they can be opened normally