Difference between revisions of "Validations"
imported>Aeric |
imported>Aeric |
||
Line 3: | Line 3: | ||
When a telephone number in your database has too many digits, it is bad information, and it slows you down. Clean data is essential to efficient performance. Data validation policies help to avoid simple mistakes, and assure that the data entering your system is sound. | When a telephone number in your database has too many digits, it is bad information, and it slows you down. Clean data is essential to efficient performance. Data validation policies help to avoid simple mistakes, and assure that the data entering your system is sound. | ||
Validation policies let you establish triggering actions, custom criteria, and error messages that are activated when data changes | Validation policies let you establish triggering actions, custom criteria, and error messages that are activated when data changes. | ||
Validation policies compare field data using formulas you create - the result is a true or false value. When the return value is true, no action is taken. When false, the system displays a custom error message (see [[#Example|Example]]). | Validation policies compare field data using formulas you create - the result is a true or false value. When the return value is true, no action is taken. When false, the system displays a custom error message (see [[#Example|Example]]). |
Revision as of 02:02, 12 January 2013
Designer > Objects > {object} > Validations
When a telephone number in your database has too many digits, it is bad information, and it slows you down. Clean data is essential to efficient performance. Data validation policies help to avoid simple mistakes, and assure that the data entering your system is sound.
Validation policies let you establish triggering actions, custom criteria, and error messages that are activated when data changes.
Validation policies compare field data using formulas you create - the result is a true or false value. When the return value is true, no action is taken. When false, the system displays a custom error message (see Example).
Sample Validation
You might check that a telephone number entered in a data field has the correct number of digits. If the number of digits is not equal to 10, an error message is displayed, and the process stops until the correction is made.
While this is a simple example of data validation, you can easily create complex and powerful validation formulas with the available picklists.
Create the Validation Criteria
For the validation criteria, enter a Formula Expression. Functions are available for all data types: date, logical, math and text. The expression you develop to create a validation policy can contain multiple fields to validate, such as ensuring that phone numbers do not exceed 10 digits or names do not contain invalid characters.
Add a Data Validation Policy to an Object
- Click Designer > Objects > {object} > Validations
- Enter a Name for the validation policy
- To enable the policy, click the Enable checkbox
- Choose a Triggering Action. The data validation policy will be applied when one of these actions is applied to the record:
- Add
- Update
- Delete
- Enter an Expression in the Validation Criteria section. The expression must evaluate to true or false. Define the condition(s) that record data must meet to trigger the validation policy. Learn more: Formula Expressions
- Field
- The field that must contain the condition. All fields contained in this object are listed.
- Operator
- Choose an operator to build an expression
- Choose Function
- Select the type of function, the specific function to use, and click the Insert button. The types of functions are:
- Date Functions
- Logical Functions
- Math Functions
- Text Functions
- Select the type of function, the specific function to use, and click the Insert button. The types of functions are:
- Click the [Check Syntax] button to validate the expression.
- Enter the Error Message that you want to appear if the data causes an error condition in the validation policy.