Forum Discussion
rsQueryTimeoutExceeded
Hi jesushmmadrid ,
Using a Composite Model can definitely help in separating the date logic while still keeping both fact tables consistently filterable, and applying group by/ summarize patterns in key measures can also reduce the size of the filter context and improve performance.
Please follow these articles for reference :
Optimization guide for Power BI - Power BI | Microsoft LearnData reduction techniques for Import modeling - Power BI | Microsoft Learn
Data reduction techniques for Import modeling - Power BI | Microsoft Learn
Regards
Super UserIt happens because USERELATIONSHIP over two fact tables and an indirect path forces the engine to evaluate a huge filter context.
The clean fix is to create two role-playing date tables, one for Admission and one for Invoice, each with an active relationship.
That removes ambiguity and makes DAX much faster. If model changes aren’t possible, try TREATAS instead of USERELATIONSHIP , it’s usually lighter on resources.
Shai Karmani | Data & Analytics
If it helped ,
please mark as resolved & give a kudo so others can find it too.
Let’s connect on LinkedIn