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

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
EoH
New Member

Unable to open pbix in Power BI Desktop

I'm unable to open a file I've been working on for some time on a Power BI report server using Power BI Desktop.

The error is:

"This file uses a composite model which combines DirectQuery sources and/or imported data. These models aren't currently supported in Power BI Report Server"

 

The file opens fine via the report server. I've only ever edited the file using the desktop client.

 

Desktop client and server are both May 2024 release.

The report should only be using DirectQuery sources (a local SQL server).

 

This happened before on a report without nearly as much data in it that I wrote off as an oddity and rebuilt; this report however, has a bit more work in it I'd rather not recreate.

1 ACCEPTED SOLUTION
EoH
New Member

Going to drop this in here in the event anyone else bumps into this particular problem:

It turns out my report did indeed switch to MixedMode because I had used the "Merge Queries as New" function; even though this is based on DirectQuery data, the resultant table is considered to be in "Import Mode".

 

Once completed, if you then save and close your report you can no longer access it using the Report Server version of Power BI Desktop when attempting to open it again (I had this report open for weeks after I had made the change and was able to keep using it just fine). Interestingly enough, the Report Server itself has no problem displaying the report - so the technology exists and is, at least somewhat, supported (or else the report wouldn't function at all).

 

To both identify and fix this:

1. Download a copy of Power BI Desktop Cloud Version

2. Open Model View

3. For each table

a. Select the table

b. Open the Properties tab and expand "Advanced"

c. Verify the Storage mode

--Once the merged query was identified as the "Import mode" table, I removed it, saved it and then was able to open the report in the Report Server version of Power BI Desktop.

 

Lesson learned! You can break your own access to a report by using "Merge/Append Queries as New". While you get warnings and are forced to change the storage mode when importing static data, this particular feature does not have the same checks and warnings associated with it. You have been warned.

 

I'll leave the obvious questions about gating this functionality, ability to break your own report, and the lack of support channels for non-premium users unasked.

View solution in original post

5 REPLIES 5
EoH
New Member

Going to drop this in here in the event anyone else bumps into this particular problem:

It turns out my report did indeed switch to MixedMode because I had used the "Merge Queries as New" function; even though this is based on DirectQuery data, the resultant table is considered to be in "Import Mode".

 

Once completed, if you then save and close your report you can no longer access it using the Report Server version of Power BI Desktop when attempting to open it again (I had this report open for weeks after I had made the change and was able to keep using it just fine). Interestingly enough, the Report Server itself has no problem displaying the report - so the technology exists and is, at least somewhat, supported (or else the report wouldn't function at all).

 

To both identify and fix this:

1. Download a copy of Power BI Desktop Cloud Version

2. Open Model View

3. For each table

a. Select the table

b. Open the Properties tab and expand "Advanced"

c. Verify the Storage mode

--Once the merged query was identified as the "Import mode" table, I removed it, saved it and then was able to open the report in the Report Server version of Power BI Desktop.

 

Lesson learned! You can break your own access to a report by using "Merge/Append Queries as New". While you get warnings and are forced to change the storage mode when importing static data, this particular feature does not have the same checks and warnings associated with it. You have been warned.

 

I'll leave the obvious questions about gating this functionality, ability to break your own report, and the lack of support channels for non-premium users unasked.

This exact sequence happened to me.  I created a nice report using direct query sources in a report server version of desktop.  I created a bridge table, saved the report and viewed the report via the portal.  The report worked fine.  One day later I went to open the report in the desktop and was told the composite data model was an issue.  I'm not sure how report server shows the report and/or desktop allows you to do something it's not going to support.  Very frustrating.  I lost a few days of work since I had left the report in the desktop for most of the week.  

 

I'm glad this note was available.  I was able to use the cloud version, delete the bridge tables, save the report and start over.

EoH
New Member

Good relative time of day greeting to you @v-xiandat-msft,

 

Thank you so much for taking the time to reply to me.

 

I apologize for not placing prominence on the line in my original post about the report ONLY using DirectQuery.

 

The file has only ever used DirectQuery from a single source of truth, exactly an SQL Server (which I did state).

 

Nothing was brought in using the "Import mode" because, well, I theoretically shouldn't have been able to without converting the entire file to Import mode - The Power BI Report Server Desktop client won't let you!

 

Since I have only ever edited this file using a client that won't let me create a composite model I'm perplexed as to how the Desktop Client determined that the model is no longer exclusively DirectQuery. Additionally: The report server runs the file just fine, loading the file into the Desktop Client directly from the report server does not change the behavior I'm experiencing.

 

I'm happy to clarify further to help find a solution!

v-xiandat-msft
Community Support
Community Support

Hi @EoH ,

Your file uses a composite model that combines DirectQuery sources and/or imported data. Unfortunately, Power BI Report Server doesn't currently support compositing.

It is recommended to use a single source of truth, such as SQL Server, and use direct query mode to complete the report.

vxiandatmsft_0-1717739242257.png

Best Regards,

Xianda Tang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I disagree with your post and assumptions.  My report was using SQL Server and Direct Query.  I created a simple Bridge table which caused the report to fail to open in Report Server.

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors