|
Hi, In our class Dossier, during the OnInitialize, a default DossierContacting is add to an EntitySet. Somehow validation becomes active and throws an exception:
Regards Paul Sinnema Diartis AG Updated at 07.07.2010 13:58:55Alex, My colleague has debugged the matter a bit further. In our Configuration object retrieved with Configurateion.Load() the Autovalidation is false. When we create a Domain with this Configuration, on the Domain the Configuration.AutoValidation = true (?). This looks like a bug to me. Regards Paul Sinnema Diartis AG Updated at 08.07.2010 7:22:04Hi Alex, This problem is blocking us at the moment. Can you give me a work-arround? We probably need to disable Validation for the moment. We can't however disable it via the Configuration as stated above. Regards Paul Sinnema Diartis AG. This thread was imported from our support forum. The original discussion may contain more detailed answer. |
Do you use auto transactions? Most likely, there is an issue with wrapping this method call by auto transaction.
Try to do the same inside manual transaction. If this will work, we'll create and fix the issue.
The bug is confirmed - value of this property isn't copied during cloning of DomainConfiguration, but cloning is used in Domain.Build. I'll try to propose the workaround shortly, or simply fix the bug - we anyway plan to publish an update today.
The only workaround I imagine is to set it using reflection after Domain.Build completion. The bug is now fixed, update will be available quite soon.
Issue: http://code.google.com/p/dataobjectsdot ... ail?id=736 (fixed)