Since my table name is different from the entity name, in v2 designer, I refer the result of "View Entity List" function to search the entity by table name.

However, I cannot find this function in v3, is this function dropped in v3? or it has an alternative ways to find entity by table name in v3?

I refer the result of "View Entity List" function to search the entity by table name.

Are you talking about finding an entity at Design time (Designer APIs), or at runtime using the generated code?

Please elaborate more and show how did you use to find the entity. Code snippet please.

We've implemented a full search system in v3. Please open the élement search' tab. You can write any linq query you want over the entire project. We added examples to each element type to get you started this replaces the entity list, as it had just 1 purpose, but sometimes you wanted other info... I'll get back to you with a query which mimics the entity list

(edit)

to get all entities and the mappings of them in a list, do: - select 'Enumerable' in element search' combo box - use this code:

return from kvp in p.GetAllEntitiesWithTheirMappingsForDatabase(SqlServerSqlClientDriverID)
       select new { EntityName = kvp.Key.FullName, MappedTarget = kvp.Value.MappedTarget==null? "Not mapped" : kvp.Value.MappedTarget.FullNameWithCatalog};

Run the query.

kvp.Key is an EntityDefinition. kvp.Value is a GroupableModelElementMapping. Please use the designer reference manual to get more details on what you can do with the project, how to obtain information and which queries to run to get what you want.

It works, thank you!!!

Can I save the query in project? Therefore, I can reuse it later and share it with my colleague.

Barry wrote:

It works, thank you!!!

Can I save the query in project? Therefore, I can reuse it later and share it with my colleague.

Unfortunately we couldn't get that in the RTM release. It sounds silly perhaps, as it sounds like a simple feature, but it was actually cumbersome to get this working with proper editing, the UI we designed for it wasn't intuitive enough, whatever we tried, so we cut it.

We hope to have a bunch of better ideas to deal with this in the next v3.x version. In the meantime you've to share the query using other means, e.g. internal documentation.