This model doesn't have a table named

[tkim]

I made changes to a view named Product in the SQL Server and when I tried to refresh the view in Power BI, it gave me an error saying "This model doesn't have a table named Product." The changes that I made were to just add a couple columns in. The view exists within my data model and when I preview the data in PowerQuery it shows up correctly. It was working before, but after the changes it stopped working and gave me this error message. What may be creating this issue?

[Pierro_Schoeman]

Having the same issue...

[Anonymous]

This solution did not work. The names are identical between the Power Query Editor and the actual PowerBI Fields section. Any other ideas please?

Error:

"The model doesn't have a table named <name of table>"

[Ragosu66]

My report presented the same problem after applying changes to step names and table names in the transformation editor. I checked the references for several cases and found a workable solution.

First identify the current table with new name whose old name is mentioned in the error message "the model doesn't have a table named ...", create a reference and name it with the old name.
Proceed with the change application and data reload, in my case, the reload was completed without any problem, applying the changes made in the PBIX and the semantic model.
Save your changes, and now proceed to delete the reference for this table and reapply the changes and save.
I assume that this is a bug, which does not correctly record in certain situations the subsequent changes of table names after applying them in the PBIX.
I hope this helps your problem.

[v-xicai]

Hi  @tkim ,

Does that make sense? If so, kindly mark my answer as a solution to help others having the similar issue and close the case. If not, let me know and I'll try to help you further.

Best regards

Amy

[v-xicai · Accepted solution]

Hi @tkim , 

You may try to rename the table in The Fields pane.

Or you may clear permissions under "Data Source settings", and establish the connection to SQL Server again.

Best Regards,

Amy

Community Support Team _ Amy

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

[ValentinLenkSBS]

I can't rename the table without first discarding all changes to the queries. Given that the error in my case occurred after a significant overhaul to the structure of the queries, that would mean redoing a lot of work. Resetting the connection permissions did not solve the issue.

Is there a method that wastes less time?