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.

[yockee]

@RobertKrisher  any technical insight regarding why one is better than another one ?

I am thinking that database trigger works on Database Tier, whereas the Attribute Validation works on Server Tier. So the the database tier will work better because it is more efficient.

But I dont know how this Attribute Validation works in Map Feature Service ? The Attribute Validation never gets published as service but how can it work when one access the data via Map Feature Service ? Where is it stored ? On the other hand, database trigger can be seen as database object in the database.

I need more explanation. Thanks

[RobertKrisher]

The attribute rule is stored in the geodatabase and is exposed through a validation service to clients. There is also the ability to choose between enforcing rules client-side, or server-side only. I recommend you do some research on attribute rules and the validation service.

[yockee]

@RobertKrisher 

"The attribute rule is stored in the geodatabase and is exposed through a validation service to clients"  

1. Where can I see the attribute rule in the geodatabase ? 

2. What is the validation service looks like ? Is it a some sort of wer services ? I need to see the object.