Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] Data Refresh not available for DirectLake models (at the table level) #999

Closed
m-kovalsky opened this issue Sep 28, 2023 · 3 comments
Assignees
Labels
issue: bug Confirmed as a bug in TE3

Comments

@m-kovalsky
Copy link

Describe the issue
When live-connected to a DirectLake model, there is no way to use the Data Refresh functionality in TE3 on a table. There is only the option to use data refresh on the whole model itself.

** Which version are you currently using? **
3.11.0.26496

Steps to reproduce the behavior:

  1. Connect to a DirectLake model
  2. Right click on a table
  3. There is no option for Refresh...

Expected behavior
Although it is commonly thought that DirectLake models do not need to be refreshed as it is managed in Fabric, this is not always the case. Adding/updating RLS necessitates 'framing' or refreshing the model. Additionally, folks can turn off the 'auto-sync' refresh option for their dataset which would that make it necessitate 'framing' (refreshes). In such a case, folks likely want individual control over which tables are synced with the lakehouse at a given time (so don't want to frame/refresh the entire model, just a table or several tables).

Desktop (please complete the following information):

  • Windows version: 11
@m-kovalsky m-kovalsky changed the title [Issue] Data Refresh not available for DirectLake models [Issue] Data Refresh not available for DirectLake models (at the table level) Sep 28, 2023
@otykier
Copy link
Collaborator

otykier commented Sep 28, 2023

Good catch! We’ll make sure the tool allows refresh of individual tables. Am I correct in my assumption that DirectLake tables only need the “Full” refresh option?

@m-kovalsky
Copy link
Author

Great, thanks Daniel! Yes, 'full' should be enough for DirectLake models. However if composite models becomes supported with DirectLake models then other processing modes will become relevant as well.

@otykier otykier added the issue: bug Confirmed as a bug in TE3 label Oct 13, 2023
@otykier
Copy link
Collaborator

otykier commented Nov 28, 2023

Fixed in 3.12.0, thanks for reporting!

@otykier otykier closed this as completed Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Confirmed as a bug in TE3
Development

No branches or pull requests

2 participants