Forum Discussion
Downloading PBIX from Service breaks dataset
- 5 years ago
After speaking with Microsoft support they were just as confounded as I was originally. However, after some research they did discover an interesting limitation outlined in the documentation.
After deployment, downloading a dataset (from the stage it's been deployed to) is not supported.
https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-process#limitations-1
So basically, at least as it stands now, it appears you cannot download a dataset from a location in the pipeline other than it's original uploaded workspace. Hopefully this will help others if they encounter the same issue.
Hi YB,
AFAIK, these notices normally appear when your report closes without saving changes. Any operations that you apply to this report? If you open a new pbix file or open this on a new device, did this notice appears again?
Please share more detailed information to help us clarify and troubleshoot your scenario:
How to Get Your Question Answered Quickly
Regards,
Xiaoxin Sheng
Hi Anonymous ,
If there is more information to provide I'm not sure what it would be but I'm open to suggestions. The steps to reproduce are quite simple.
- Upload report to Test workspace.
- Deploy to production using pipeline
- Download report from Production workspace
- Open on Power BI Desktop
The issue is happening on more than one report across multiple pipelines and workspaces. As I mentioned, I'm less concerned about the message and more about why it's happening. If there are no rules applied to the pipeline from test to production, there should be no changes being done to the report. Furthermore, the report runs fine in all environments. The question is why is power bi desktop is detecting a change at all? Also, why would accepting the change completely remove the attached dataset?
Sure I could just click on cancel and be on my merry way but someone who doesn't realize this could cause themselves a lot of grief. I'm trying to determine if this is a bug with the desktop or an issue with the service. Unless I'm missing something completely obvious this should not be happening at all. With that being said I did open a ticket with support as suggested by Greg. If I find a solution with support I will post it here but I am completely open to suggestions if someone has some ideas.
Thanks,