Skip to main content

Live edit of Direct Lake models in Power BI Desktop

Direct Lake speeds up data-driven decisions by unlocking incredible performance directly against OneLake while ensuring maximum data reusability across Fabric. Last month, we announced a major update for developers working on Direct Lake models: Live editing of Power BI semantic models in Direct Lake mode. Now, you can use Power BI Desktop to edit Direct Lake semantic models, improving your data modeling experience and allowing export to Power BI Project (PBIP) for professional development workflows.

With live edit every modification is applied to the semantic model in the workspace, ensuring a seamless and efficient workflow.


Get started

Start by enabling the preview feature, go to File > Options and settings > Options > Preview features and check the box next to “Live edit of Power BI semantic models in Direct Lake mode

Once the preview feature is enabled, restart Power BI Desktop, open OneLake datahub:


Then, choose the Direct Lake semantic model you want to modify and click on Edit:

By opening the model for editing in Power BI Desktop, you can directly modify the semantic model. Since it’s a Live Edit, all changes are instantly applied to the semantic model in the Fabric workspace without needing to save. Changes include all modeling tasks, such as renaming tables/columns, add/remove tables from Lakehousecreating measures, and creating calculation groupsDAX query view is available to run DAX queries to preview data and test measures before saving them to the model.

Enterprise development with Power BI Project (PBIP)

This feature also allows for the integration of Power BI Project with Direct Lake semantic models. You can export the definition of your semantic model after opening it for editing to a Power BI Project, which provides a local copy of the semantic model and report metadata, enabling source control with Git and deployment mechanisms such as Fabric Git Integration.

Go to File > Export > Power BI Project and export it as a Power BI Project:



When opening a Power BI Project with a Direct Lake semantic model, you need to choose a remote semantic model in a Fabric workspace, as direct lake semantic models cannot run locally in Power BI Desktop.


Each developer should choose their own isolated semantic model in a development workspace to prevent conflicts during development. Use Git as the central metadata repository, deploying the semantic model metadata to the final workspace via Fabric Git or Fabric APIs.


Comments

Popular posts from this blog

SSRS INTERVIEW QUESTIONS

Q: What is SSRS? Ø   SSRS or SQL Server Reporting Service is a server-based report generation software systems from Microsoft and is part of Microsoft BI. Ø   It is used for preparing and delivering interactive and variety of reports. Ø   It is administered through an web based interface. Ø   Reporting services utilizes a web service interface for supporting and developing of customized reporting applications. Ø   SSRS lets you create very rich reports (Tabular/Graphical/Interactive) from various datasources with rich data visualization (Charts, Maps, sparklines) Ø   SSRS allows are reports to be exported in various formats (Excel, PDF, word etc) Q: Explain SSRS Architecture? Reporting services architecture comprises of integrated components. It is a multi-tiered, included with application, server and data layers. This architecture is scalable and modular. A single installation can be used across multiple computers. It includes the fo...

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got...

Failed to execute the package or element. Build errors were encountered

Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package