Forum Discussion
PowerBI visual breaks
Hi PPGGG,
Thank you for reaching out to the Microsoft Fabric Forum Community.
In this scenario, the most effective solution would be to create a central dataset that brings together the required data such as Project and Company using a common key like MasterID. This can be done using dataflows, SQL views, or by building a combined dataset in Power BI. Using this single, unified dataset in your report helps avoid relationship issues and broken visuals.
Best regards,
Prasanna Kumar
Hi PPGGG ,
Yeah, this happens a lot with composite models in Power BI, especially when you’re mixing Import and DirectQuery sources. Even if you’ve set up the relationships, Power BI visuals can break when you try to use fields from more than one DirectQuery source in a single visual. It’s a known limitation — the engine just can’t resolve relationships between multiple DQ sources at once.
The suggestion above is definitely right: the most reliable workaround is to import at least one of your DirectQuery tables into the model. That way, your visual only references a single DirectQuery source, which Power BI supports. If you absolutely need to use both tables in DQ mode together, you might need to rethink your model or use dataflows/pre-joined tables as prep.
If you want, I can help walk through importing a table or restructuring your visual logic — just let me know!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI
Can you suggest any other solution because this characteristics are required to be in a separate data model which need to be used as direct query only