Thank you for the feedback.
We understand that this error can be very frustrating. For that reason we have created a validation rule
that will help you identify all of those cases, and a validation action that can fix them for you. I am not sure if we can actually make this process more automated, as in the absence of a primary key column if would be risky for OpenAccess ORM to try guessing the best option - it is much better to leave that choice to you. As for the specific case of the database views, we do plan to improve the process of reading them from the database so that we can have an idea what should the identity be. However, I cannot yet provide you with a time frame for releasing that feature.
What we have done recently for Q3 2012 (already live) is to change the warning
that a persistent type doesn't have a primary key to an error, which means that even on the Visual Designer surface you know that the model will have serious problems during runtime.
I hope that helps.
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.