semantic model refresh in case of framing in fabric

[powerbiexpert22]

do i need to refresh my semantic model in case of direct lake connection like we do in case of import mode to get the latest data from darabase ? i am referring to framing process which occurs in case of direct lake connection as mentioned in below url

https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview#framing

[Bhuwanreddy999]

Hello @cengizhanarslan , Firstly I would like to thank you for giving insights on this issue. we have recently encountered issue with 

Direct Lake framing failure. we are pulling data from the azure databricks into lakehouse1 and from that lakehouse1 we are writing into lakehouse 2 with overwrite  so everyday pipelines runs at 1 time with latest data into lakehouse 2. so currently the reports which built using direct lake mode are intermittently failing with below error message . failures also occuring at random times and it fails for 2 to 3 times and next time it will success.

An error has occurred while framing the dataset error: Failed to save modifications to the server. Error returned: ' Unexpected parquet exception occurred. Class: 'ParquetStatusException' Status: 'IOError' Message: 'Encountered Azure error while accessing lake file, StatusCode = 0, ErrorCode = , Reason = ' Unexpected parquet exception occurred. Class: 'ParquetStatusException' Status: 'IOError' Message: 'Encountered Azure error while accessing lake file, StatusCode = 0, ErrorCode = , Reason = ' The current operation was cancelled because another operation in the transaction failed. 

could you please share your insights on this.

[powerbiexpert22]

Hi @cengizhanarslan ,

what if "Keep your Direct Lake data up to date" setting is OFF, do i need to refesh the semantic model and how many refreshes are possible? also , i could not locate this setting in official documentation 

[cengizhanarslan · Accepted solution]

Then you must trigger a semantic model refresh to make the model aware of newly written Delta files. But keep it mind that this is not an Import refresh. It is a lightweight metadata refresh (often called framing), which re-reads Delta table metadata, updates file references, does NOT re-import all data into VertiPaq.

[v-menakakota]

Hi @powerbiexpert22 ,
Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank  @cengizhanarslan  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you 

   

Best Regards, 
Community Support Team  

[v-menakakota]

Hi @powerbiexpert22 ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you 

   

Best Regards, 
Community Support Team 

[cengizhanarslan]

Direct Lake models are not a cached snapshot of data like Import mode. Instead, they read Delta tables in OneLake directly. So if your semantic model is in Direct Lake mode and “Keep your Direct Lake data up to date” setting is ON,
then fresh data is reflected automatically in reports, no scheduled refresh required to get the latest Lakehouse changes.