Allow Power BI Designer to open a Dataset or Report published in online Power BI repository
If you setup a data source using the Power BI Analysis Services Connector that shows up in the Power BI online Dataset repository you should allow the use of that dataset directly from the Power BI Designer.
This will allow you to publish reports using the already shared dataset and it also gives you a better experience querying a tabular data source then the Power BI Designer does now when connecting directly to the tabular instance.
I would say this should also apply to any other 3rd party data source created there for the likes GitHub, Salesforce, etc.
You should also be able to open reports that have been published and edited in the service in the same way.
We are currently working on the support to re-open pbix files from desktop.
Kyle Hale commented
Can this be marked complete, given the release of this functionality in April 2017?
Any further update on this. We are in need to edit the data in Sales force from PowerBI
Pratima Arwey commented
Whats the point of single sign on and cloud hosting when online reports and datasets can't be accessed from Desktop.
Since we are already signed in to the Power BI online repository to publish reports from Power BI Desktop, it should be a simple task to add an option under file to "Open File From Power BI Online" as in other data visualization programs (e.g. Tableau).
Aaron Shumaker commented
I want to point out that it's not just being able to edit datasets/reports published previously, but when creating a new report, the user should be able to select the existing gateway/data source instead of specifying server/database names for SSAS.
Aaron Shumaker commented
Spent alot of time putting together all the pieces of the DW/SSAS/PowerBI stack, got gateway and data source setup, only to find that PowerBI Desktop doesn't leverage the gateway or data source.
This results in several very disappointing realizations:
1) Desktop users need DIRECT access to SSAS. Not all users are on the same local network, and so PowerBI was a great option to create a common cloud based reporting portal. SSAS is on a VM that is not on the same network as the users, so without a lot of additional networking they will not be able to access SSAS directly. The whole point of the Gateway installation was to give PowerBI access to SSAS without any complex networking/VPN setup.
2) Lay users have to know server names/database names to connect to SSAS. If they could simply browse to and select an existing Datasource/Gateway that was configured in the portal by IT, they don't need to know any "magic values".
3) Decentralizes management of the datasource/connection, taking management out of the hands of IT. As other commenters point out, DB or server name changes will disrupt a multitude of published reports/dashboards, and since they were not created from a centrally managed datasource/gateway, it will be difficult to update them all easily.
The data scientists/experts who would be creating and publishing reports/dashboards do not have direct access to SSAS. Why bother creating a gateway if it is not going to be leveraged?
Desktop right now doesn't fit into an Enterprise architecture. As DrJohnT points out, you are not giving IT proper control over the datasource. Generally with this type of platform you have a few data scientists/analysts creating dashaboards, and publishing those for business users to consume. IT needs to be able to expose a common data source for those analysts to use. Thus allowing IT to modify the properties of the data source later if needed. Having users create their own data sources is going to quickly turn into a maintenance nightmare. They shouldn't need to know about server names or database names.
Jenifer Jones commented
Please update with news on this feature. This is very important to the user community
Will, we need this functionality please as it is important that one can get the file in a .pbix and have it worked on by external consultants.
Jeff Garcia commented
Please update with any news available about this feature.
Marc Lelijveld commented
Is there any news about this topic? Since it's on the radar for over a year!
Ian Watkins commented
Any news on this feature coming along?
Key question in my mind is how to handle the following senario: if a dataset was published by a user and later IT move the database to another server, how would they get access to the PowerBI dataset to change the connection details – especially of the original user has left the company. Seems the feature requested here would help
In my scenario, I have many members added in the group .but we want only admin can edit the report and rest all should only view the report.
but Power BI is giving editing option to each and every member added?
kindly help on this
Any news on this topic? As it is on radar since January 23.
Jason Brugger commented
Glad this is planned. This feature is essential to modeling of datasets that originate with the REST API or as ASA Outputs.
Pawel Potasinski commented
I would say the same is about reports - I don't see a way to effectively maintain (edit) the reports because I need the original .pbix / .xlsx file. Instead you could allow to open published datasets and reports in Power BI Desktop and Excel.
Paul C commented
Its very strange that the Power BI Designer can't work with Power BI data sources - I would have expected it to have been the first data source supported. We too have created data sources using the REST API and the limitation is very frustrating.
Martin ter Horst commented
We'd love to be able to pull down a report or dashboard from the service into the desktop application for advanced editing, and then republish it. We could then truly collaborate on report and dashboard design both in the service as well as on the desktop