I'm sure this is by intent, but validation not happening on unchanged records.
Thta sounds reasonable, but its causing us a problem. We have an import process that loads data from an external system. It may not find values for all the fields that the verification rules say should have values. The import doesn't use DevForce.
The idea is that the data loads in an invalid state, and the first time the record is accessed, the user is forced to fix it. However, if the user brings up a view that contains parents and children, and doesn't "touch" the child that is missing data, the verification won't catch it on a save.
We also have an export process that can only run if all the data is there, so when they hit export, I run down the tree and call the VerificationEngine.Execute on each object. The objects that are missing data do not fail verification.
Ideas?