Constraint executing before calculation error

OliverSandoval_p

Hello,

We need to have a calculation and constrain triggered on insert. The constraint evaluates whether the field(that has been calculated with a calculation rule) is a certain value. 

This works in a file geodatabase, but not an sql geodatabase.

So in the sql database the constraint is evaluated first before the calculation has taken place, so you can never insert a new record. Is there a possible explanation for this, or is there some documentation that I'm missing that I can be directed to? Thank you for your time! 

OliverSandoval_p

There was a tech support case that I opened, it took about 1.5 months, but we were able to narrow it down to the way the sql database was created. The attribute rules were tested on sde files that were copied and pasted, feature table in the same database worked fine with the attribute rules if it was created, not copied. Before this I was able to create an alternate script that worked fine either way.