Allow Power BI Designer to open a Dataset or Report published in online Power BI repository

[Tom_Marek]

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.

[ian_watkins]

Any news on this feature coming along?

[Marc_lelijveld1]

Is there any news about this topic? Since it's on the radar for over a year!

[jgarciabu1]

Please update with any news available about this feature.

[Michaelm]

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.

[jejones]

Please update with news on this feature. This is very important to the user community

[AaronLS]

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 main

[AaronLS]

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.

[alm5084]

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).

[josh_flory1]

Any news????

[Pratima_arwey]

Whats the point of single sign on and cloud hosting when online reports and datasets can't be accessed from Desktop.