Field Names

For topics that list all of the fields in a detail page, use the following standardized text: “An object name has the following fields, listed in alphabetical order.” If it includes fields that can be hidden in page layouts or field-level security, include the following standardized text: “Depending on your page layout and field-level security settings, some fields may not be visible or editable.”

Labels

Use the element’s exact label when you refer to user interface elements, but remove any end punctuation, such as an ellipsis. Retain any punctuation that’s not at the end of the label.

Example

Click Add... to browse for files on your local computer.

Capitalization

Use title-style capitalization for field names. Don't capitalize field when it is part of a name, unless it’s in a heading or considered part of the proper name.

Example

Import your data into the Lead Source field.

Formatting

  • In documentation, field names display in a monospace font.
  • In user interface text, don't use special formatting when referring to field names.
  • When listing fields with descriptions, use a table. Don't use a bullet list or definition list.

Custom Fields

When referring to a custom field that you recommend users create, use the same style conventions as when referring to a standard Salesforce field.

Prepositions

When referring to fields in relation to objects, use on instead of in.

Example

When you create a custom field on a standard object, add the custom field to your package explicitly.