[DevExpress Support Team: CLONED FROM T686387: Web - New objects created in Batch Edit mode disappear when clicking Save Changes]
Thank you Anatol !
The changing of the the base class fixed the issue, however my challenge is not the update of the database as the app is still in development, but in using the BaseObject at all as it is not available in the ORM editor by default.
For most of my apps I am using the ORM editor for the model design as I find it much easier to build and maintain. Also I find that the on boarding and orientation time for new developers it is much faster.
In order to introduce the BaseObject in the ORM editor I will have to draw explicit inheritance connection with every single class which creates a tons of mess on the designer canvas, especially with models with lots of classes.
Is there any compromise solution which can achieve the same result.
For example is there a way to inherit the BaseObject without explicitly placing it on the designer canvas and connecting with other classes or Is there a way to implement similar key values generation mechanism for XPObject classes.
I tried application.LinkNewObjectToParentImmediately = true, but it didn't worked.
Thank you for your support,
This is one of the ORM Data Model Wizard and Designer enhancements we have planned for 2019 in our roadmap:
Moreover, we have already made it possible for XAF users to select DevExpress.Persistent.BaseImpl.BaseObject in the BaseClass field in v19.1. The following image shows what it looks like in the night build. Red dots show the types to be removed from the editor in the final release. The BaseObject will also be available under the PersistentBase item for faster access.
What do you think?
Please refer to the T532524: DevExpress.Persistent.BaseIml.BaseObjects in ORM Data Model Designer Wizard thread where we discussed this question and suggested a workaround. Hope it will help. If you have any additional questions, let me know.