The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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