Forum Discussion
Advocate IIDownload .pbix greyed out
Hi biswedishdevil,
You an go to My Workspace, then create a content pack, publish to that specific app group follow Create and publish an organizational content pack (tutorial).
Then in the app workspace, assume you have edit permission, then you can use Get Data-> My organization to get content pack, the report will display in that app workspace.
Best Regards,
Qiuyun Yu
Community SupportHi biswedishdevil,
You an go to My Workspace, then create a content pack, publish to that specific app group follow Create and publish an organizational content pack (tutorial).
Then in the app workspace, assume you have edit permission, then you can use Get Data-> My organization to get content pack, the report will display in that app workspace.
Best Regards,
Qiuyun Yu
Advocate ICan we just call PBI an Alpha at this point? I've had nothing but headaches from this **bleep** product.
It's over a year later and this stupid limitation is still there.
mvanderlee There are additional options to copy reports from one workspace to another via powershell commands if you are trying to accomplish moving reports to other locations. Otherwise, follow the design of the product and build reports in the Desktop in order to have the additional flexibility. There are a small number of use cases where you have to build reports in Service, and in those cases where you want to, you will be limited by what you can create (measures, etc), and will need to work with more advanced techniques to move things around.
Hello Anonymous ,
I do not agree on that. This is the functionality requested by many of our users who are not PowerUsers. It is even more confusing to allow users to create these reports on PowerBI service and restrict them from publishing to Premium workspace to share with (Free) users.
Not understanding, why shouldn't this be allowed? What will we lose?
Thanks!
Follow the design? The design is poolry thought out and constructed with too many limitations. Period.
John_L_EdwardsAdvocate III
I'll just mention as a follow-up that we gave up on using the tool. Getting data out of our corporate architecture and into a place where Power BI could use it proved more or less indefensible to our IT team. It was deemed a security hazard. So at that point the shortcomings just piled on too high to continue.
It's replacement, believe it or not, is Excel.
We drive data to a template Excel file via WebFOCUS/I-Way (where you can export every doggone thing in any direction you want by the way) and let Excel's map feature present our color gradients in the main tab. I had it up and running in production in about a day.
I think we need to wait for Power BI to reach version 3.51 before we give it another go.
- Anonymous v-qiuyu-msft What if we are creating Dataset using API, it should allow the download in that case at least ? Can we download it in that case ? Currently, it is greyed out in that case as well.
- Show the Navigation pane
- Select the Workspace
- Scroll Down to the 'Datasets'
- Highlight the report's Dataset
- Click on the ellipses
- Select 'Download .pbix'
nirvana_mokshImpactful Individual
I totally agree with Anonymous, the use cases for building reports directly on the Service are very limited and mostly these are for "Power Users" to whom some kind of PBI content that is created on the Desktop level is published/delivered on the Service and they are deriving variants of the original report that was developed on PBI Desktop.
Also, can't expect a product to work some other way when it is explicitly mentioned that it works one way. Documentation will be counter intutive if that is how products were to work.
- John_L_Edwards
With all due respect, that's a load of hooey. Why on Earth would this product exist without an ability to export your source code from the web version? This sounds like a decision made by the sales & marketing team.
I had to learn on the web version, now have the desktop version. All my prior content is stranded on the web version. Graying out the button that says "Download a .pbix copy" was just one more way of thumbing their nose at me.
Clearly NOT SOLVED. This tool needs a LOT of work. There's no unity of design. Typical Microsoft product where they've thrown 10,000 parts into a pile and expect it to be a running car afterwards.
John_L_Edwards I can certainly understand the frustration, but to use your own analogy this is more like you jumping into a brand new car not understanding how it works and blaming the manufacturer for your accident because you didn't read the manual and operate it correctly. Since the creation of the product, the bulk of everything a report author needs to do is in the Desktop, the Service currently provides a fraction of the functionality required to produce reports. We all get frustrated, and we're all here to help each other out. No need to start slamming the product or the team that supports it.
