Defining Field Types

When creating a new custom field, you need to choose whether the field will be defined as Normal or Computed. You may see the term derived in place of computed throughout this course and in product documentation. The two words should be considered interchangeable.

What are the differences between those two options?

• Are Reportable by default
• Value is either defined by the end users in the UI, or it can have a calculated value
• There are limited amounts of fields per class

• Value of the field must always be calculated based on specific logic or inherited from another existing field value
• The field is not editable in the UI by end users
• Fields cannot be made reportable
• In Procurement, computed fields are commonly used for exporting custom object unique IDs to an ERP
• There are limited amounts of computed fields per site

• Derived fields can be recognized in Field Configuration by special icon.

Each custom field has a unique identifier with the prefix cus_. The field name cannot contain any special characters.

The remaining part of the name is calculated from the field label, however, both values can be manually changed during field creation.

Note:

• On each class, field technical names must be unique.
• Once the field is published, the field name and type cannot be modified.

When creating a custom field, you need to decide which field type to use. Depending on the class you are customizing, the following options may be available in the Type drop down in addition to the standard field types that may appear:

Access What field types are available for custom field requests for a comprehensive list of custom field types and their descriptions.