Attribute Validation / Calculation using Arcade or Database Trigger

[yockee]

I am just wondering if Attribute Validation is better with Database Trigger or Arcade.

Suppose I want to do Attribute Validation about the value of one coloumn that depends on the value of another coloumn OR maybe I want to limit the data entry of a coloumn OR maybe I want to populate a date coloumn automatically.

In a scenario in which the data (stored in SDE) have to be accessed by many people via Map / Feature Service, which one is more suitable in term of fastness and reliability ? What are the considerations in choosing a particular method ? 

Thank you

[RPGIS]

Hi @yockee,

I don't typically use validation rules simply because the workflows that we have generally will account for all the edits that come in from the field. Typically validation is mostly for verifying that the data that is entered meets a certain criteria.

It is usually best to create calculations that will account for certain things rather than try and force the editor to fill in the information. The solutions that we have created automatically account for certain behaviors and so there isn't a need to for validation.

The other thing is if you are concerned with certain types of edits then you could try and create a constraint rule instead. The benefit of a constraint rule is that you can customize messages will appear to the editors and letting them know what needs to be corrected in order to continue editing.

[RobertKrisher]

The attribute rule is going to be more reliable and have a better user experience, especially if you're working with data that is versioned or coming in through mobile workflows. You can even make some attribute rules available to mobile users when they are offline, so even when they're editing a local copy of the data integrity is still enforced.