The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello community,
I'm running across this issue when openning my pbix file, which used to work fine. Getting this error messge all of the sudden.
Solved! Go to Solution.
Hi @Russo
You're getting this error because the PBIX file uses a composite model – it combines DirectQuery and Import tables, or multiple DirectQuery sources.
Power BI Report Server doesn't support composite models, so the file can't be opened in that environment.
Open the file using regular Power BI Desktop (not the Report Server version) – it should open fine.
Go to Model View, click each table, and check the Storage Mode.
If even one table is Import while others are DirectQuery – that's what triggers the error.
A common cause is using “Merge Queries as New” in Power Query – it silently creates an Import table even if the source was DirectQuery.
If the report is meant for Power BI Service – you're good. Composite models are fully supported there.
If you're publishing to Power BI Report Server:
Make sure all tables are either Import or DirectQuery from a single source.
Delete any merged/imported tables that cause mixed storage.
Rebuild the logic using SQL views or clean DirectQuery connections.
If nothing works – just open a support ticket and let them investigate based on your specific environment.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi @Russo ,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks @Ritaf1983 , for those valuable insights for this thread.
The error you are seeing is because your report uses a composite model (a mix of Import and DirectQuery), which is not supported in Power BI Report Server. This setup works in the Power BI Service, but Report Server only allows fully Import or fully DirectQuery models. To resolve this, you may either adjust your model to use just one mode or switch to publishing it in the Power BI Service. Please refer the link here for more information:
power-bi-report-server-feature-comparison
I hope this resolve your query.If so,give us kudos and consider accepting it as solution.
Regards,
Pallavi G.
I believe my company uses Power BI Service, this should be accepted. Do you know how I can verify?
Hi @Russo ,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks @Ritaf1983 , for those valuable insights for this thread.
The error you are seeing is because your report uses a composite model (a mix of Import and DirectQuery), which is not supported in Power BI Report Server. This setup works in the Power BI Service, but Report Server only allows fully Import or fully DirectQuery models. To resolve this, you may either adjust your model to use just one mode or switch to publishing it in the Power BI Service. Please refer the link here for more information:
power-bi-report-server-feature-comparison
I hope this resolve your query.If so,give us kudos and consider accepting it as solution.
Regards,
Pallavi G.
Hi @Russo
You're getting this error because the PBIX file uses a composite model – it combines DirectQuery and Import tables, or multiple DirectQuery sources.
Power BI Report Server doesn't support composite models, so the file can't be opened in that environment.
Open the file using regular Power BI Desktop (not the Report Server version) – it should open fine.
Go to Model View, click each table, and check the Storage Mode.
If even one table is Import while others are DirectQuery – that's what triggers the error.
A common cause is using “Merge Queries as New” in Power Query – it silently creates an Import table even if the source was DirectQuery.
If the report is meant for Power BI Service – you're good. Composite models are fully supported there.
If you're publishing to Power BI Report Server:
Make sure all tables are either Import or DirectQuery from a single source.
Delete any merged/imported tables that cause mixed storage.
Rebuild the logic using SQL views or clean DirectQuery connections.
If nothing works – just open a support ticket and let them investigate based on your specific environment.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
User | Count |
---|---|
78 | |
73 | |
38 | |
30 | |
28 |
User | Count |
---|---|
107 | |
100 | |
55 | |
49 | |
45 |