Currently, attribute rules are only enforced and applied if edits are made through ArcGIS Pro or a Branch Versioned Feature Service. This is okay, but since Attribute Rules are essentially a method for implementing database triggers, they should be enforced at the Database level. How the data is edited on a Feature Class in a File or Enterprise Geodatabase should be (mostly) irrelevant.
If I want to update it with a SQL script, that shouldn't be a problem.
If I want to update it with a Python script, that shouldn't be a problem.
If I want to update it in ArcMap, ArcGlobe, ArcScene, that shouldn't be a problem.
Bake the logic directly into the File and Enterprise Geodatabase so that I can update the data however I want and not have to worry about what client my customer is using to edit my data with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.