Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

0
BernatAgulloAnt

Report using composite model not displaying correctly on embedded capacity

Submitted by on ‎11-15-2023 04:06 AM
Hello,
 
The mother company of a customer has an intranet page connected to a workspace to consume the reports that are published there. 
 
All good with the exception of a report that is built using DQ over two other datasets also published in the same workspace. (They insist on having all visuals on the same report page). That report cannot be displayed in the intranet site.
 
In the Power BI Service the report shows fine -- not super-slow or anything like that.
 
Is there any limitation regarding composite models and Power BI Embedded that prevents this scenario from working?
 
Regards!
Status: Delivered

Hi @BernatAgulloAnt ,

 

Yes, there are some limitations when it comes to using composite models with Power BI Embedded. One of the key limitations is that using Power BI Embedded with datasets that include a DirectQuery connection to an Azure Analysis Services model isn’t currently supported.

Composite models allow a report to have two or more data connections from different source groups. These source groups can be one or more DirectQuery connections and an import connection, two or more DirectQuery connections, or any combination thereof. When a tabular model connects to another tabular model, it’s known as chaining. However, when a model connects to a tabular model but doesn’t extend it with additional data, it’s not a composite model.

If the report is working fine in the Power BI Service but not in the embedded scenario, it might be due to these limitations. You may want to consider restructuring your data or report to avoid these limitations.

 

Use composite models in Power BI Desktop - Power BI | Microsoft Learn

Composite model guidance in Power BI Desktop - Power BI | Microsoft Learn

 

Best Regards,
Community Support Team _ Caitlyn

See more ideas labeled with:
1 Comment (1 New)
Comments
v-xiaoyan-msft
Community Support
Community Support
‎11-16-2023 01:20 AM
Status changed to: Delivered

Hi @BernatAgulloAnt ,

 

Yes, there are some limitations when it comes to using composite models with Power BI Embedded. One of the key limitations is that using Power BI Embedded with datasets that include a DirectQuery connection to an Azure Analysis Services model isn’t currently supported.

Composite models allow a report to have two or more data connections from different source groups. These source groups can be one or more DirectQuery connections and an import connection, two or more DirectQuery connections, or any combination thereof. When a tabular model connects to another tabular model, it’s known as chaining. However, when a model connects to a tabular model but doesn’t extend it with additional data, it’s not a composite model.

If the report is working fine in the Power BI Service but not in the embedded scenario, it might be due to these limitations. You may want to consider restructuring your data or report to avoid these limitations.

 

Use composite models in Power BI Desktop - Power BI | Microsoft Learn

Composite model guidance in Power BI Desktop - Power BI | Microsoft Learn

 

Best Regards,
Community Support Team _ Caitlyn

Idea Statuses