"The entity name doesn't exist" error in Dynamics 365 views

You open a view on a custom table and get “The entity name doesn’t exist”. Most likely the view has an object type code (ObjectTypeCode) stored that doesn’t belong to this environment. It tends to happen when you move solutions between environments, because custom tables don’t necessarily get the same code in each one. Standard tables like account or contact won’t give you this problem, since their code never changes.

To fix it, first get the real ObjectTypeCode of the table in your environment:

https://YOUR-ENV.crm4.dynamics.com/api/data/v9.2/EntityDefinitions?$select=LogicalName,ObjectTypeCode&$filter=LogicalName eq 'table_name'

Then open XrmToolBox → View Designer, load the table and, in each view, edit the XML to replace the old number in the object attribute with the one you just copied. Save, publish, and the view should open normally again.