...
Select the layer that the rule should act (required).
In the example above the rule is applied to the Trees table.
Selecting the desired layer from the dropdown list.
Define the criteria that must be met prior to applying the test (optional).
In the example above, the test should only be applied if the field 'Species' has a value equal to 'HWD' for hardwoods. If the 'Species' has a value that is null or not equal to 'HWD', the test portion of the rule will not even be assessed.
Many rules do not require criteria because they should always be true
If a criteria is needed:
Select the field(s) from the field selection box. If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names.
Select the criteria operator from the dropdown list.
Enter the text or number in the value which will be evaluated.
Typically this value is simply typed in with no punctuation (e.g., LP).
When testing if a field or fields have a null value, enter as 'Null' (capitol N, without quotes).
If the value is coming from another field (uncommon), enter in the field within curly brackets { } (e.g., '{Saw_Stopper}' without the quotes.
If the operator is ‘in’ enter multiple values in a comma separated list (e.g., 1,2,3,4). Do not include spaces. Do not add parenthesis around the list.
If the value is a Date, use the Unix time stamp (in milliseconds). For example, if assessing if a date is before Jan 1, 2020 the value would be 1577836800000. To convert between a human-readable date and Unix time stamp see https://www.epochconverter.com/ .
If no criteria is needed because the test should always be applied (see examples 1, 2 and 6 above):
Uncheck the 'Include criteria' checkbox
Define the main rule logic
Select the field(s) from the field selection box. If more than one field is needed, click on the first field name, then hold CTRL and click on additional field names.
Select the criteria operator from the dropdown list.
Enter the text or number in the value which will be evaluated.
Typically this value is simply typed in with no punctuation (e.g., LP).
When testing if a field or fields have a null value, enter as 'Null' (capitol N, without quotes).
If the value is coming from another field (uncommon), enter in the field within curly brackets { } (e.g., '{Saw_Stopper}' without the quotes.
If the operator is ‘in’ enter multiple values in a comma separated list (e.g., 1,2,3,4). Do not include spaces. Do not add parenthesis around the list.
If the value is a Date, use the Unix time stamp (in milliseconds). For example, if assessing if a date is before Jan 1, 2020 the value would be 1577836800000. To convert between a human-readable date and Unix time stamp see https://www.epochconverter.com/ .
Select the error type
Select 'Error' or 'Warning' from the dropdown list
Errors will prevent the user from saving the record (or closing the tree list)
Warnings will be displayed once to the user, then will allow save (and close of tree list)
Enter the error (or warning) message to display to the user
Enter the full message that should be displayed to the user if the features does not pass the validation rule
This should be a short message that will help the user address the problem. It is best to reference field Aliases (rather than field names) so it matches what the user sees on their screen. Providing the expected value helps users enter correct values.
...