Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

DirectQuery Refresh Broken update january 2018

Hi,

Seems to me there's a bug in the new January update.
I have a report using DirectQuery, and when I refresh my model it keeps saying:
"Connecting to tables from more than one database isn't supported in DirectQuery mode.".
If I rollback my installation to PBI December, the refresh works, as I don't have multiple datasources in my model.


Thanks in advance.

 

Frank

Status: Accepted
Comments
dsynan
Advocate III

Same

Anonymous
Not applicable

Same here - Please fix this ASAP

v-jiascu-msft
Employee

Hi @Goofr,

 

There is a similar case here. I tested again. I still can't reproduce it. Could someone give more details?

My test scenario:

1. A view gets data from two tables in two databases.

2. Direct Query to SQL Server.

No errors with refreshing.

 

Best Regards,

Dale

Vicky_Song
Impactful Individual
Status changed to: Needs Info
 
Goofr
Advocate IV

Hello,

 

Can I send you an email?

I've got a simple example showing the bug.

 

Frank

v-jiascu-msft
Employee

Hi @Goofr,

 

You can upload the file to a cloud drive like GoogleDrive, OneDrive. Then send me a message with the link. Since it's in Direct Query mode, I can't open it locally. Can you give some introductions please?

1. SQL Server version;

2. Sql tables or views;

3. Any visuals;

4. Any additional step in the Query Editor.

 

Best Regards,

Dale

Goofr
Advocate IV

Hi @v-jiascu-msft,

 

PBI DQ bug example

 

Open the file and hit refresh, you will get the warning/error.

I use an Azure SQL Premium RS db, and connect via the model to 3 tables.

 

Thanks

 

Frank

v-jiascu-msft
Employee

Hi Frank, @Goofr,

 

Thank you for your info. Though I can't use your file without credentials, I can reproduce this issue now. Please delete the link unless you think it's good with you. (Please be aware of your privacy. ) 

The root cause is the customized sql statements. I will submit a report to the Product team to find out what happened. I will update here later.

 

Best Regards,

Dale

Goofr
Advocate IV

OK thanks,

file deleted 🙂

Birdjo
Resolver II
I have the same issue. I uninstalled Power BI and then installed the December 2017 version.