Refer to the Error showing detail view ticket and the http://www.devexpress.com/Support/WhatsNew/DXperience/files/13.1.2.bc.xml#BC1850 breaking change for more details.
We have closed this ticket because another page addresses its subject:
How to avoid the "There is already node with Id 'YourClassName_ListView" error when having several classes with the same name, but declared within different namespacesCore - Make it possible to find a View node by its short identifier
Answers approved by DevExpress Support
We have implemented the functionality described in this ticket. It will be included in our next update(s).
Please check back and leave a comment to this response to let us know whether or not this solution addresses your concerns.
The generation algorithm for IModelView.Id values has been changed in version 13.1 (see B236715).
You can enable resolving short identifiers in the Application Model used in previous versions by setting the static ModelNodeIdHelper.ProcessShortViewIDs property to true.
In code (e.g., in a ViewController), to check whether or not a short identifier matches a full identifier in code, use the static ModelNodeIdHelper.IsViewIdMatch method. You can also use the ModelNodeIdHelper.GetXXXViewId methods to obtain a full View identifier by a business object type.
- v13.1.5Download Official Update
Starting with version 13.1.6 the generation mechanism will stay unchanged (short identifiers like Customer_ListView will be used), while having the capability to resolve a name conflict in advanced scenarios. Hence, the options described in this thread are marked as obsolete.
Please refer to the Core - Introduce an ability to have two or more classes with one and the same name, but declared within different assemblies thread for more details.
I want to thank you all customers who provided their great feedback during this time and also want to apologize for all the inconvenience here.
hey folks, will there be a time when we can create a target view id string with multiple IDs, perhaps separated by commas? This is quite valuable in the context of those who use view variants
Thank you for the feedback, Drew. You may want to add the Core - Make it possible to activate the same ViewController or Action for multiple Views or target object types ticket into your Support Center favorites list.