General Conventions
All Naming Conventions Are RFC 2119 and RFC 6919 compliant.
- All field API names MUST be written in English, even when the label is in another language.
- All field API names MUST be written in PascalCase.
- Fields SHOULD NOT contain an underscore in the fields name, except where explicitly defined otherwise in these conventions.
- Fields generally MUST (but you probably won't) contain a description.
- In all cases where the entire purpose of the field is not evident by reading the name, the field MUST contain a description.
- If the purpose of the field is ambiguous, the field MUST contain a help text. In cases where the purpose is clear, the help text COULD also be defined for clarity's sake.
- Field API names should respect the following prefixes and suffixes.2 Prefixes and Suffixes SHALL NOT be prepended by an underscore.
| Field Type | Prefix | Suffix |
|---|---|---|
| MasterDetail | Ref |
|
| Lookup | Ref |
|
| Formula | Auto |
|
| Rollup Summary | Auto |
|
| Filled by automation (APEX)1 | Trig |
|
| Picklist or Multipicklist | Pick |
|
| Boolean |
Is or IsCan3
|