Forum Discussion
Direct Lake Semantic Model not showing latest data
Direct Lake Semantic Model not showing latest data:
I have refreshed the semantic model several times.
I have turned off Cache ( it was by default - turned OFF)
Also cleared Cache from my PBI Report. (Although latest data i am checking by creating new report from semantic model itself (by pulling relavant fields), its not showing latest data.
Can you pls help
Hi A454A ,
Your understanding is largely accurate, and your explanation reflects how this functions in Fabric. When using Direct Lake with a Warehouse, it still relies on the SQL analytics endpoint, which can introduce a brief delay before new data becomes visible. While this delay is typically minimal, it can vary based on workload, data volume, and update frequency.
You are also correct regarding semantic model refreshes. In Direct Lake mode, a refresh primarily updates metadata rather than performing a full data reload as Import mode does, so new data may not be immediately available if the backend has not yet synchronized. Clearing the report cache does not affect this, as the delay occurs before the semantic model receives the data.
The distinction you mentioned is important. When accessing Delta tables directly without the SQL endpoint, data generally appears much faster. The behavior you're observing is specific to scenarios involving Warehouses or SQL endpoints.
Thank you.
6 Replies
Hi this is direct lake on Fabric Warehouse!
- InsightsByV
Super User
+1 tayloramy
I have this similar query -
I have also created a Power BI report with Directlake mode (for testing this mode) where data is coming from Mirrorring. Now I have also analysed that the data doesnt get refreshed instantly. What can be the reason for it?
One thing I can think of is the latency but that doesnt seem to be an issue. Can someone guide?
Hi A454A ,
Your understanding is largely accurate, and your explanation reflects how this functions in Fabric. When using Direct Lake with a Warehouse, it still relies on the SQL analytics endpoint, which can introduce a brief delay before new data becomes visible. While this delay is typically minimal, it can vary based on workload, data volume, and update frequency.
You are also correct regarding semantic model refreshes. In Direct Lake mode, a refresh primarily updates metadata rather than performing a full data reload as Import mode does, so new data may not be immediately available if the backend has not yet synchronized. Clearing the report cache does not affect this, as the delay occurs before the semantic model receives the data.
The distinction you mentioned is important. When accessing Delta tables directly without the SQL endpoint, data generally appears much faster. The behavior you're observing is specific to scenarios involving Warehouses or SQL endpoints.
Thank you.Hi A454A ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.Hi A454A ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
