Latest data in Lakehouse not showing up in Direct Lake Power BI report

[daxman]

I have a Power BI report that is connected to the default dataset for a Lakehouse. Using Gen2 dataflows, I load more data into the Lakehouse (using the "replace" method in the dataflow).

When I open the SQL Endpoint, I can confirm that new data has been brought into the Lakehouse. However, my Power BI report is not seeing the new data. It appears to have cached the previous data that was in the Lakehouse. If I wait until the next day, I will see the data, but my understanding is that with Direct Lake mode, I should be able to see that new data instantly.

Is there something else I should be doing? Or is this a bug with the Lakehouse's built in dataset?

[amcpherson]

I am having the same issue as well. SQL endpoint shows correct data but the direct lake mode report does not. Was there a solution for this. I do not see an option to refresh my report either.

[ananthkrishna99]

Hi @daxman , AFIK, Default dataset doesn't support direct lake mode now, it works based on Direct Query. For Direct Lake mode you have to create a custom dataset and for that also you have to refresh the dataset once Lakehouse tables are loaded with data so that Dataset will point to the Latest parquet files.

[daxman]

Interesting, where have you seen that? From everything I've seen, connecting "live" to the default dataset for a Lakehouse is supposed to leverage Direct Lake mode, and only reverts to Direct Query as a fall back method.

The report performance has been good so far, which leads me to believe it's probably not Direct Query.

There is also no way for me to "refresh" the default Lakehouse dataset.

[anselmojg]

Same issue with the default dataset... The tables in the lakehouse have been updated but the dataset only shows older data in both Direct Lake (report created in the Service) and Direct Query (report created in desktop)