|For each field in the schema, you can specify some or all of the following conversion properties: |
Alternate text string for displayBase Data Definition
Data definition with BASE attribute set. Field settings are inherited from this base definition.Required
Enable to make the field a required field. This field must contain a user entry.Data Type
Select a data type for the field.Enumeration Values
A comma-separated list of choices.Hidden
Enable to hide the field.Read Only
Enable to make field a display field. No data can be entered in such a field.Formatting Expression
Select a format for the field from the list of formats. For example, if you choose the format expression DateTimeFormat(FormatString), the string FormatString is replaced with the evaluated version of what the user entered in the Format Expression Argument input before it is passed to the Formatter.Validate Expression
To provide data entry validation of the field, select a validation expression. Choose one of the validate expressions to apply to the field data being submitted. The validate method implements server-side validation and operates on the value returned by the translate method (if translate is used).
Note: The following date comparison methods are available to support date validation: Date>today, Date>=today, Date=today, Date<=today, Date<today.
Select one of the available translate expressions to apply to the field data being submitted. Translating refers to modifying user input for storage as data. For example, a user may insert dashes when entering a Social Security number in a form. A translate method could remove the hyphens from the user input, creating a value that can now be stored as data. Similarly, the Credit Card 16 digit expression removes hyphen (-) and space characters from a string and ignores errors.