Viewing Fields

1.From the Configuration console, click Build > Business Objects.

2.Open a business object. The application opens the workspace for the selected business object.

3.Select the Fields tab. The application displays a list of fields.

Field Description
Field Name A unique name without spaces or special characters.
Display Name The name that appears to users.
Type The type, such as binary, Unicode text, text, integer, DateTime, short, and so on. See Form Field Types.
Unique Assigns a unique ID to a record. This ID is unique across all instances (records) in the business object table. This is the same as the unique index used in a Microsoft SQL database.


Allows a NULL value to be entered in a field. Values are not enforced in this field, but when they are defined, they must be unique (even though Unique is not checked).


Stores field values in the database. When checkbox is cleared, it permits the field to be evaluated at runtime but not store its values.


Does not show this field in the application. You cannot use this when creating a form. This option is typically activated by default and is of particular use in group and member business objects.


Makes this field searchable. For example, number fields often produce unexpected results when performing a text search. You can check this field to make your field search correctly. An example is the IncidentNumber field in the Incident business object.


Specifies that the field is part of a database index.

Full-text Indexed

Text and binary fields can be full-text indexed. The application indexes unique words for fields that are marked as full-text indexed and uses them in full-text search and simple keyword search in the business object workspace.

Note: We recommend setting only a limited number of fields to full-text indexed, because setting too many fields can cause performance issues.


When selected, any changes to this field are audited in the audit stream.


Uses a validation list. Select a list from the drop-down list. The field must be marked as Unicode to be used as the pick list for a validated text field. Also, the data type between the stored field in the named validation list, and a validated field, must match.

For example, if the named validation list is defined against a text field, but the user is attempting to use it for a number field, the validation does not work. You can also translate values from a validated pick list. If a field is validated and the field from where it is fetching data is marked Is Localizable, then click the Values link in the Validated section, and add the translated values for the supported languages.