Power BI Service Connector Bug.

[daandamhuis]

Hi All, 

I installed the lastest version of the Power BI Desktop and I noticed that everytime I select the Power BI Service data connector it automaticly switches the SSAS connector after selecting a Power BI Service source. This means that I cannot switch from a test source to a production source. 

Version: 2.50.4859.782 64-bit (september 2017)

With kind regards, 

Daan Damhuis

[v-jiascu-msft]

@daandamhuis,

Hi Daan Damhuis,

It's a live connection, which is just similar with SSAS live connection. You can reference powerbi-desktop-report-lifecycle-datasets/#limitations-and-considerations for details.

>>>Since this is a live connection, left-navigation and modeling are disabled, similar to the behavior when connected to SQL Server Analysis Services.

According to my test, it's easy to switch the data source. Open the connector, select the new dataset you want. Done.

Best Regards!

Dale

[daandamhuis]

This doesn't work in my version. 

If i select the Power BI Online Service connector, it automaticly changes the connection type to a SSAS Live connection. So when I publish the report, it automaticly creates a new data source. Which is not the desired effect, and beside that I cannot change to a datasource in an other workspace. So when I publish from Acceptance to Production, it creates another data source in the production workspace.

In the end, I have 12 PBI data sources in the workspace for two cubes.

[v-jiascu-msft]

Hi @daandamhuis,

1. Is your original data source SSAS?

2. Why do you switch the dataset from one to another? We can say the connector Power BI Service aims at sharing a single dataset. Why not create reports based on the production dataset?

3. Could you please post some snapshots?

Best Regards!

Dale

[daandamhuis]

FYI, this worked before in de August Version. 

1. Is your original data source SSAS?

Yes, Tabular. 

2. Why do you switch the dataset from one to another?

Deploy the same report to several workspaces and just have 1 data source for 1 SSAS Cube in each workspace instead of having serveral because each time a Data Set doesn't exists with the report name, Power BI just creates a new one (See 4). 

We can say the connector Power BI Service aims at sharing a single dataset. Why not create reports based on the production dataset? <= Because we do User Acceptance tests of Model and Reports in a specific Workspace / App before deployed these to the production envoironment. 

3. Could you please post some snapshots?

1) Get Data - Power BI Service2) Select Data Source - Power BI Service3) Connected - Live Connection to SSAS instead of Power BI Online4) Report Deployed - New Data Source Created instead of using the TST data source that I pointed to in the "Get Data"

[daandamhuis]

No one has a solution or the same issue?

[v-jiascu-msft]

Hi @daandamhuis,

I tested it again today. It works in Power BI Desktop July as the documentation describes. I will submit a report at once. The workaround could be creating reports in the Service. Sorry for any inconvenience. Any updates will be posted here.

Best Regards!

Dale

[v-jiascu-msft · Accepted solution]

Hi @daandamhuis,

According to my test, the issue is gone in the latest Version: 2.52.4921.581 64-bit (November 2017). You can try it out.

Best Regards!

Dale