Fields

Designer > Data > Objects > {object} > Fields

Fields are attributes of a Custom Object, and are used to contain many types of data:

• Fields are defined by giving them a label and specifying a Field Display Type
• New fields can be added to the Form Layout canvas
• Fields can have Role-Based Visibility, meaning that the field data is visible only to users who have permission rights for that field
• Fields can have a Default Value defined, which pre-populates the field in the data entry form (Form Layout)

• Default values can be created with Formula Fields

• Fields created by Users are listed as Custom in the Type column

Users that have the Customize Objects permission can edit Fields

Add Fields

Fields can be added to an Object from the Fields tab. The fields that are displayed to users in different roles, and the positioning of those fields, is defined in Forms.

Add a Field from the Fields Tab

Add Field

To Remove a Field from a Layout:

1. Click Designer > Data & Presentation > Object > {object}
2. In the Forms tab, hover the mouse over the field to remove, and click the Remove Field button in the floating toolbar

   

The field is removed from the layout, but it remains available in the object and is moved to the Pick Existing section of the Elements Sidebar. Fields can be reused in this layout or any new layouts.

Delete a Field

1. Click the field name.
2. Click [Delete].
   A confirmation dialog opens.
3. Click [OK] to delete the field.

This is a permanent deletion, and cannot be restored.

Field Audit Log

When the Field Audit Log option is enabled, you list the fields to be audited. Changes to those fields are then added to each record's Activity History.

Users that have the Customize Objects permission can set the Field Audit Log.

Users that have the Manage Audit Log permission can view the Audit Log

When a field is modified, the following information is added to the activity history:

• Field label
• Original field value
• New field value
• Who changed it
• When it happened

Considerations

• Creation dates are not logged.
• An entry is added to the activity history for each audited field that changes. (If three fields change, three entries are added.)
• For the Cases object and several other System Objects, all fields are audited, by default.
• For Custom Objects, field auditing is turned off, by default.

Enable the Field Audit Log

1. Go to > Objects > {object} > Field Audit Log Settings
2. Click Enable Field Audit Log
   The list of object fields appears.
3. Click Track All Fields, or leave that option unselected and click the checkbox next to each field to be audited.
   (Choose up to 20 fields per object.)
4. Click [Save]

Learn more: Activity History

Role-Based Field-Level Permission Control

Role Based Permission Control

For Developers

Visit these pages for a list predefined fields in

• CRM Objects
• Built-in Objects

Guidelines for Add/Update Field Value

The Order of precedence of field properties (#1 takes precedence over #2, etc.):

1. Always Required
2. Field Visibility
3. Display Attribute

Add/Update Field Value

• For the API/UI calls, the Always Required property applies, even if the field is defined as hidden/read only via Form Layout or Field Visibility settings

• Fields defined as Hidden/Read-Only via Field Visibility settings can not be added/updated from the UI, and should not be added/updated from the API

• Fields defined as Hidden/Read-Only via Display Attributes are considered only for UI calls (but not API calls)

• Hidden Fields can be updated through the scripting

• Fields defined as part of Custom Objects can be set to Read-Only or Hidden via Field Visibility settings

Log Access Violation

• When fields defined as Hidden/Read-Only via Field Visibility settings are used in an API/UI request, the entry can be logged in the Audit Log, provided that the Enhanced Security Audit is enabled

[[Category:Template:Features]]