Dataset Workload Import Error After Switching from Direct Query to Snowflake Import Model

[drgenius]

Hi everyone,

I have a Power BI report that I want to publish to my Fabric workspace.

When I try to upload it, I get the following error: Dataset Workload failed to import the dataset with dataset id 7894a0d1-f8c2-4a33-9881-f41f76fe081b. Neither 'model.bim' nor anything with 'definition/.tmdl' were found.*

Some context: this report was originally built using Direct Query. I have since migrated it to use Import mode with a Snowflake connection (pulling from Snowflake tables instead). Despite this change, the definition folder appears to be empty, which I believe is the root cause of the error. My questions are: Is this a known issue when switching a report from Direct Query to Import mode? Could the semantic model definition not have been regenerated properly during that transition? Is there a way to fix this without rebuilding the report from scratch? For example, by republishing in a way that forces the model.bim or definition/*.tmdl files to be recreated? 

Any guidance would be appreciated.

Thanks in advance!

[Kedar_Pande]

@drgenius 

Open PBIX in Desktop, File > Save As > Power BI Project (.pbip). This regenerates model.bim and TMDL files from scratch.

DirectQuery to Import mode transition corrupts semantic model metadata. PBIP forces full rebuild. Then publish normally.

[MFelix]

Hi @drgenius ,

Is this a thing report connected to a semantic model on the service or a report that as the semantic model in the same file?

Looking at the description that you reference that the definition folder appears to be empty I believe that you are refering to a report that is connected to the published model and not has the semantic model attach to it, and also that you are saving it has a PBIP file.

If you are connecting to an online semantic model my suggestion is the following:

• Make a backup of your report
• Create a new report connected to the semantic model online (can be a blank report)
• Copy the the folder for the semantic model to the folder of the report that is having the problem

This will make the connections to be change to the new model.

[Ritaf1983 · Accepted solution]

Hi @drgenius 

This error typically occurs because the model's metadata (model.bim or the definition folder) was not packaged correctly during the transition from Direct Query to Import mode. This is a known local state-saving issue, and you do not need to rebuild the report.

To resolve this, you can force Power BI to regenerate the missing semantic model definitions using one of the following methods:

First, if you are uploading the file manually via the Fabric web interface, try using the 'Publish' button directly from Power BI Desktop. This forces a recompilation and repackaging of the file.

If that fails, force a metadata rewrite by opening the file in Desktop, making a minor model change (like adding a blank measure), and using "Save As" to save it as a Power BI Project file (.pbip). This forces the engine to recreate the folder structure, including the missing definition folder.

Alternatively, navigate to File -> Options and settings -> Options -> Preview features. Toggle the "Store semantic model using TMDL format" setting (turn it on if it is off, or vice versa), restart Power BI Desktop, and save the file again to trigger the metadata generation.

Finally, if you are in a Fabric or Premium workspace, you can bypass the PBIX upload mechanism entirely. Open the local file, connect to the model using an external tool like Tabular Editor, and deploy the model directly to the Workspace via the XMLA Endpoint.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[drgenius]

Hi @Ritaf1983,

Thank you very much for your help!!
I managed to fix it with this suggestion

"Alternatively, navigate to File -> Options and settings -> Options -> Preview features. Toggle the "Store semantic model using TMDL format" setting (turn it on if it is off, or vice versa), restart Power BI Desktop, and save the file again to trigger the metadata generation."