In our 2.6 project, we have Typed List names that are the same as our Entity names: i.e. Account (Entity), Account (TypedList).
We've converted the project from 2.6 to 3.1, open the project in the 3.1 and the designer displays the Entity and Typed List from within the '' project.
After performing a 'Refresh Relational Model from a Database' ... our TypedList name gets changed from Account to Account. It appears that the TypedList is changed from Account to Account because of duplicate checking?
Our 2.6 projects have many cases where the TypedList name is the same as the Entity name. Since the default naming convention for generated code is AccountEntity, AccountTypedList, AccountTypedView, etc., I expected that the designer would be able to handle the same name from within the same group? i.e. group name "A", Entity "B" should not conflict with group name A, TypedList "B".
The workaround seems to be to create a new group name and push the Account TypedList to the new group so there will not be a name conflict but this seems clunky. The only other option is to rename the duplicate TypedLists and refactor our code?
