Forum Discussion
Identical semantic models, but only one has an error
I made some minor changes to a semantic model and republished it. It started giving me errors. First, "This dataset includes a dynamic data source." Great, I can fix that, and did. Then, "Could not resolve query definition. This error often happens after the Column or Entity was renamed or deleted."
So, I took the same semantic model, published it to the same workspace under a different name (think ModelName_test), and it refreshes just fine.
My initial instinct is to delete the semantic model and try again, but I can't because it is referenced by another report (not one of mine, unfortunately), and therefore can't be deleted.
So... what would you do next?
Hi JrBIAnalyst
please try below points.
In your PBIX file, temporarily add back the removed column, even if it's just a dummy or blank column with the same name and type. Then, publish the file again using the exact dataset name to replace the old one. This should allow the Service to accept the publish without errors, as the schema will match what is expected. Once everything is stable, you can use Tabular Editor or the XMLA endpoint to safely remove the unused column from the dataset object, preventing issues with downstream reports.If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Thanks.
7 Replies
- FBergamaschi
Super User
IN the minor changes you made to the semantic model, did you cancel any column or table?
If this helped, please consider giving kudos and mark as a solution
me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Yes, I did remove a column. But the underlying issue is that for some reason, having removed the column results in the data model no longer publishing correctly. That's the part that I really need help with. Given that I can't delete the data model because of its downstream use, how do I force the new model to publish correctly?
- collinq
Hey JrBIAnalyst ,
As FBergamaschi metnioned, perhaps a column was renamed? Or, did you delete a column OR, did you delete or rename the dataset? Hi JrBIAnalyst
Thank you for reaching out to the Microsoft Fabric Forum Community.
collinq FBergamaschi Thanks for your inputs.
As requested by the users, please provide the details they asked for so we can analyze what happened and work towards resolving it. We are happy to assist you.Hi JrBIAnalyst
Kindly share the requested details so we can analyze the issue and work towards a resolution. We’ll be glad to assist you.Hi JrBIAnalyst
please try below points.
In your PBIX file, temporarily add back the removed column, even if it's just a dummy or blank column with the same name and type. Then, publish the file again using the exact dataset name to replace the old one. This should allow the Service to accept the publish without errors, as the schema will match what is expected. Once everything is stable, you can use Tabular Editor or the XMLA endpoint to safely remove the unused column from the dataset object, preventing issues with downstream reports.If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Thanks.
