Another Fabric loss?
I'm making a play with my title since there's a section for Fabric Wins here. I previously posted about issues I've experienced with Fabric. And i'm returning again to share another.
We are trying to create a Direct Lake model to a Fabric lakehouse. And the table list in the lakehouse is cut off about halfway through when we try to connect to it in Power BI desktop. So we can't actually build a model in desktop because the list doesn't have all the tables.
Apparently it's a known issue... SINCE MAY!!!!!
Anyway. Our current work around is to go into the lakehouse in Service, click create new semantic model and connect to all the tables we need in Service. Mind you, you cannot download this model after it's created (unlike models you create from the "new item" option in your workspace that can only use csv and excel as data sources). So we can't download the model pbix from service to do anything with it.
We don't want to be limited to editing in Service. So we have to connect to the published model we created in service in Power BI desktop and use the Edit option in the connection screen.
Thank goodness for Live Editing of Service semantic models in Power BI.
Why not just always edit in Service??? Good question.. because we prefer desktop. lol. Plain and simple.
So it's an issue, but it has a workaround.
But c'mon Microsoft, you know this is buggy and has been since May. Push an update through :)
Anyone else just plain prefer desktop over service? Just me?
Give me your thoughts below.
4
7 comments
Lori Keller
5
Another Fabric loss?
Learn Microsoft Fabric
skool.com/microsoft-fabric
Helping passionate analysts, data engineers, data scientists (& more) to advance their careers on the Microsoft Fabric platform.
Leaderboard (30-day)
Powered by