The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
For the last month I notice a issue with loading reports. It comes up with an error saying unable to load the model. Its not consistent and just seems to happen at random times during the day. I have a ticket open. Anyone else having this issue?
I also had this issue recently. I'll share my process below, but the short answer is that I had to rebuild the entire dataset, which meant copying queries, calculated cols, and measures, and then re-doing model changes, sort columns, parameters, and whatever else I have forgotten to mention. I was then able to connect a report (previously failing to load) to this new dataset, and all appears to be working.
Now the longer story.
I had a dataset with two thin reports connected, published to a workspace shared with another user (Admin) and an email distribution list (Viewer).
(This workspace already has multiple datasets and reports, which the viewers access with no problem.)
The new reports work find for the Admins in the workspace. Unfortunately, the new reports would not load for the Viewers. They gave the error “Unable to load the model”.
What to do?
My conclusion at this point is that it's the particular dataset file, and that cloning it clones whatever is corrupted in the file. Hence my decision to rebuild it.
I wish I knew what was wrong with the initial file, to avoid repeating this debacle. The only thing I can point to is that Desktop was hanging (not crashing) when I was working the previous few weeks. For example, I'd pull out a field from a visual's field well, then drag another in. And nothing would happen. And Desktop would become nonresponsive. (If I had two Desktop instances running, both became non-responsive.) I thought maybe it was the Dec 2021 update. But apparently it was something wonky in that dataset .pbix.
I'd love to hear if anyone else has insight. I can't imagine the frustration and overall loss of productivity we would see if everyone resorted to rebuilding datasets when hit with this error.
The data models are not very big. 4 - 6 visuals in a report page. I opened a ticket and was told the Product Team is aware of a known issue.
I am also having this issue.