Fields can be marked as mandatory, meaning they must contain a value before the record can be saved. Mandatory fields are marked with a field status indicator before the label.

Before you begin

Role required: personalize_dictionary

About this task

A mandatory field that is pre-populated by the platform with default data, such as a value from a client script, does not display the indicator. If you delete this value from the field, however, the indicator appears. The color of the indicator depends on the field state.

Using a dictionary entry to make a field mandatory does not work when using WebServices. You can use a data policy instead. For more information on data policies, see Data policy.

Procedure

  1. Right-click the field's label in the form and select Configure Dictionary.
  2. In the Dictionary form, select the Mandatory check box.
  3. Click Update.

    The next time the form is opened, a field status indicator appears next to the field label, indicating that a value is mandatory. If the mandatory field is pre-populated for any reason, the mandatory field indicator does not appear.

    Mandatory fields are global. The field is marked as mandatory everywhere it appears in a form.

    Making a True/False mandatory will have no effect. True/False fields are always considered to have a value. A selected check box has a value of true and an unselected check box has a value of false. Either of these values satisfies the requirement of a mandatory field.

    A form can be saved with an empty mandatory field if that field is a reference field, and if the parent field is also blank. However, if the mandatory reference field shows a value from the parent field, then the form cannot be saved if this value is deleted. If the value in the referenced field is changed, the value for that field is changed everywhere it appears.

  4. (Optional) Use dictionary override>override mandatory to make a field that is mandatory only in the child table and not the parent table.