direct lake

2 Topics

report data is not visible
I have created and share the report but end user is not able to see the data. there is no RLS implemented. user have read access to workspace,lakehouse,sql end point,semantic model and report Large semantic model format:yes model lineage: lkh->semantic model->report Underlying Error: Missing_References Activity ID: cdb86897-5cc9-444c-9e0b-70a86cbce09c Correlation ID: 760f05d0-7eb4-e805-cfac-4ce83e7301a7 Request ID: 319ee4a9-fee8-4d82-4186-c08c69663697 Time: Fri Feb 20 2026 08:52:12 GMT+0400 (Gulf Standard Time) Service version: 13.0.27650.51 Client version: 2602.1.27898-train
safrasmusthafa
6 months ago Place Report Server
3.9KViews
0likes
6Comments
Request for Improved Report Publishing Experience with Direct Lake Semantic Models
I’m encountering a significant limitation when working with Power BI reports connected to Direct Lake semantic models (via Fabric Lakehouse). After migrating a dataset from an Import model to Direct Lake using ALM Toolkit, I can no longer replace the existing report in the Power BI Service by publishing from Power BI Desktop — even though the dataset is correctly updated and the report is connected to the same semantic model. Issue: Publishing from Desktop only replaces the dataset, not the report. The report visuals remain unchanged, even though the PBIX contains updated pages. This behavior is inconsistent with reports using Import or DirectQuery models, where publishing replaces both dataset and report. Manual editing in the Power BI Service is not a viable alternative due to limited functionality and the complexity of the report. Deleting and re-uploading the report breaks bookmarks, links, and Analyze in Excel connections, which is unacceptable in a production environment. Request: Please consider enabling one or more of the following: Allow full report replacement from Desktop for reports connected to Direct Lake models, with a warning if bookmarks or personal views exist. Provide a “safe replace” option that updates report visuals while preserving user bookmarks and links. Improve documentation and tooling around managing reports connected to shared semantic models (especially Direct Lake). Enable Deployment Pipelines or ALM Toolkit to update both dataset and report in a single operation for Direct Lake scenarios. This limitation is a major blocker for teams adopting Fabric and Direct Lake, and it undermines the benefits of centralized semantic models. Thank you for considering this feedback.
Solved
aggiemusicag
1 year ago Place Desktop
617Views
0likes
3Comments