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 UserHi jesushmmadrid
Your issue comes from having two date paths, the function USERELATIONSHIP makes the engine work too hard, which causes timeouts.
I suggest couple options to get it solved:
Best option → use two separate Date tables (one for Admission, one for Invoice).
Or replace USERELATIONSHIP with TREATAS, which is lighter.
Also check cross‑filters between fact tables and pre‑aggregate invoice lines if they’re too detailed.
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡