DevForce Community Forum : Validation not happening on unchanged records http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : Validation not happening on unchanged records Mon, 13 Apr 2026 17:36:47 -700 Fri, 22 Jul 2011 14:47:22 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=2840 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Validation not happening on unchanged records : Hi mikedfox;Actually as far as... http://www.ideablade.com/forum/forum_posts.asp?TID=2840&PID=11268#11268 Author: DenisK
Subject: 2840
Posted: 22-Jul-2011 at 2:47pm

Hi mikedfox;

Actually as far as I know, validation does happen on an unchanged entity. Please see below for my test.

      var cust = new Customer();
      Assert.IsTrue(cust.EntityAspect.EntityState.IsDetached());
      _em1.AddEntity(cust);
      Assert.IsTrue(cust.EntityAspect.EntityState.IsAdded());
      cust.EntityAspect.AcceptChanges();
      Assert.IsTrue(cust.EntityAspect.EntityState.IsUnchanged());
      var vrc = _em1.VerifierEngine.Execute(cust);
      Assert.IsTrue(vrc.HasErrors);
      Assert.IsTrue(vrc.Errors.Count > 0);

It also works for a detached entity, that is, an entity that has not been added yet to an EntityManager. Maybe if you can tell me what's different between my test and your use case? Also what version are you using?
]]> Fri, 22 Jul 2011 14:47:22 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2840&PID=11268#11268 Validation not happening on unchanged records : I'm sure this is by intent,... http://www.ideablade.com/forum/forum_posts.asp?TID=2840&PID=11264#11264 Author: mikedfox
Subject: 2840
Posted: 21-Jul-2011 at 12:53pm

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?
 
 
 
 
]]> Thu, 21 Jul 2011 12:53:50 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2840&PID=11264#11264