[DevExpress Support Team: CLONED FROM Q241649: Validation - Rules for aggregated child objects are checked when saving a master object in a Detail View]
Hi,
So, if I would want to disable this application-wide, I simply omit type check?
Would that be proper approach or is there a better way to accomplish this?
Reason I need this, customers have imported data from previous application which fail many of the validation rules defined in our application.
Because of that, they can not insert new data for records which contain failing records in their nested collection. It even disables fixing this errors because if there are more than one failing objects in a collection it is impossible to fix any data since validation always fails (on other records).
And since there are several dozen of objects like that, I would simply prefer to disable validation for non-edited objects - and also it is not intuitive to our customers that validation errors arise for records they are not changing and it is not possible to explain aggregated collections to average Joe in accounting.
Regards,
Mario