Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Scenario
Solved! Go to Solution.
Hey! Yes... this is doable, but not with a single table switching modes automatically. In Power BI you achieve this using a composite model with Hybrid Tables (Incremental Refresh + Real-time).
Recommended approach:
Use one fact table.
Configure Incremental Refresh.
Store the last 13 months in Import.
Keep older data as DirectQuery (real-time partition).
Use a normal Date slicer that shows all dates.
Power BI will automatically route queries:
Last 13 months → Import (fast)
Older dates → DirectQuery (on demand)
Also important to remember: DirectQuery should mainly be used when you truly need real-time or near real-time data. If your dataset refreshes daily (or less frequently), Import mode is usually the better choice for performance, stability, and lower source-system load.
Hope that help,
Best Regards,
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.
Thank you for reaching out to the Microsoft Fabric community forum.
I would also like to thank you @kushanNa and @RicardoTraNa for your active participation and for sharing solutions within the community forum.
I hope the information provided helps resolve your issue. If you have any further questions or need additional assistance, please feel free to contact us. We are always here to help.
Best regards,
Community Support Team.
Hey! Yes... this is doable, but not with a single table switching modes automatically. In Power BI you achieve this using a composite model with Hybrid Tables (Incremental Refresh + Real-time).
Recommended approach:
Use one fact table.
Configure Incremental Refresh.
Store the last 13 months in Import.
Keep older data as DirectQuery (real-time partition).
Use a normal Date slicer that shows all dates.
Power BI will automatically route queries:
Last 13 months → Import (fast)
Older dates → DirectQuery (on demand)
Also important to remember: DirectQuery should mainly be used when you truly need real-time or near real-time data. If your dataset refreshes daily (or less frequently), Import mode is usually the better choice for performance, stability, and lower source-system load.
Hope that help,
Best Regards,
I kinda feel like you are looking something similar to incremental refresh , please check if this helps : https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 43 | |
| 39 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 30 | |
| 23 |