Ashish Gunjan on 02 Dec 2024 22:34:34
We are migrating from Import, Direct Query and Composite models to Direct Lake. In this process, we are facing an issue where the datasetid gets changed as we can not deploy to the same dataset. This is causing issues for the self-serve thousands of Excel and Power BI desktop reports created by end users. This Direct Lake migration has become a pain for them as they need to rebind the reports again which is a time consuming task.
- Comments (1)
RE: DatasetID should not change when migrating to Direct Lake model
Please let us know if there is a workaround to solve for this. This is now allowing customer to scale the Direct Lake solution to existing datasets and reports.