Only $35.99/year

Salesforce Certification

Terms in this set (295)

Auto Number - A system-generated sequence number that uses a display format you define. The number is automatically incremented for each new record.

Formula - A read-only field that derives its value from a formula expression you define. The formula field is updated when any of the source fields change.

Roll-Up Summary - A read-only field that displays the sum, minimum, or maximum value of a field in a related list or the record count of all records listed in a related list.

Lookup Relationship - Creates a relationship that links this object to another object. The relationship field allows users to click on a lookup icon to select a value from a popup list. The other object is the source of the values in the list.

Master-Detail Relationship - Creates a special type of parent-child relationship between this object (the child, or "detail") and another object (the parent, or "master") where:
The relationship field is required on all detail records.
The ownership and sharing of a detail record are determined by the master record.

When a user deletes the master record, all detail records are deleted.

You can create rollup summary fields on the master record to summarize the detail records.

The relationship field allows users to click on a lookup icon to select a value from a popup list. The master object is the source of the values in the list.

External Lookup Relationship - Creates a relationship that links this object to an external object whose data is stored in an external data source.

Checkbox - Allows users to select a True (checked) or False (unchecked) value.

Currency - Allows users to enter a dollar or other currency amount and automatically formats the field as a currency amount. This can be useful if you export data to Excel or another spreadsheet.

Date - Allows users to enter a date or pick a date from a popup calendar.

Date/Time - Allows users to enter a date and time, or pick a date from a popup calendar. When users click a date in the popup, that date and the current time are entered into the Date/Time field.

Email - Allows users to enter an email address, which is validated to ensure proper format. If this field is specified for a contact or lead, users can choose the address when clicking Send an Email. Note that custom email addresses cannot be used for mass emails.

Geolocation - Allows users to define locations. Includes latitude and longitude components, and can be used to calculate distance.
Number - Allows users to enter any number. Leading zeros are removed.

Percent - Allows users to enter a percentage number, for example, '10' and automatically adds the percent sign to the number.

Phone - Allows users to enter any phone number. Automatically formats it as a phone number.

Picklist - Allows users to select a value from a list you define.

Picklist (Multi-Select) - Allows users to select multiple values from a list you define.

Text - Allows users to enter any combination of letters and numbers.

Text Area - Allows users to enter up to 255 characters on separate lines.

Text Area (Long) - Allows users to enter up to 131,072 characters on separate lines.

Text Area (Rich) - Allows users to enter formatted text, add images and links. Up to 131,072 characters on separate lines.

Text (Encrypted) - Allows users to enter any combination of letters and numbers and store them in encrypted form.

URL - Allows users to enter any valid website address. When users click on the field, the URL will open in a separate browser window.
(1:n) — A parent-child relationship in which the master object controls certain behaviors of the detail object:
When a record of the master object is deleted, its related detail records are also deleted.

The Owner field on the detail object is not available and is automatically set to the owner of its associated master record. Custom objects on the detail side of a master-detail relationship cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
The detail record inherits the sharing and security settings of its master record.

The master-detail relationship field is required on the page layout of the detail record.

By default, records can't be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.

You can define master-detail relationships between custom objects or between a custom object and a standard object. However, the standard object cannot be on the detail side of a relationship with a custom object. In addition, you cannot create a master-detail relationship in which the User or Lead objects are the master.

When you define a master-detail relationship, the custom object on which you are working is the detail side. Its data can appear as a custom related list on page layouts for the other object.

Many-to-many — You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa. For example, you may have a custom object called "Bug" that relates to the standard case object such that a bug could be related to multiple cases and a case could also be related to multiple bugs. To create a many-to-many relationship, simply create a custom junction object with two master-detail relationship fields, each linking to the objects you want to relate. See the Salesforce online help for details.
Custom objects with two master-detail relationships are supported in API version 11 and later.

Starting in API version 34.0, the JunctionIdList field type lets you manipulate the many-to-many relationship of an entity directly. You no longer need to manipulate underlying junction entity records. JunctionIdList fields can be queried and updated like any other field on the entity. Queries or updates to JunctionIdList fields act as queries or updates to the underlying junction entity records. Fields of type JunctionIdList appear in the WSDL as an unbounded array of type ID. JunctionIdList is implemented in the Task and Event objects.
Enable "Limit to Items I Own" Search Checkbox - If this setting is enabled, the Limit to Items I Own option is available to users. The option allows users to include only records for which they are the record owner when entering search queries in the sidebar.

Enable Document Content Search - If this setting is enabled, users can perform a full-text document search. When a new document is uploaded or an old one is replaced, its contents are available as search terms to retrieve the document. This setting applies only to searches for the document object.

Enable Search Optimization - if your Content is Mostly in Japanese, Chinese, or Korean If this setting is enabled, search is optimized for the Chinese, Japanese, and Korean languages in the sidebar search. It affects sidebar search and the account search for Find Duplicates on a lead record in sidebar search and global search.

Use Recently Viewed User Records for Blank and Auto-Complete Lookups - If this setting is enabled, the list of records that are returned from a user auto-complete lookup and from a blank user lookup is taken from the user's recently viewed user records. This setting applies only to lookups in the user object. If this setting isn't enabled, the dialog box shows a list of recently accessed user records from across the org.

Enable Drop-Down List for Sidebar Search If this setting is enabled, a drop-down appears for users to choose whether to search within tags, within a specific object, or across all objects.

Enable Sidebar Search Auto-Complete - If this setting is enabled, when users start typing search terms, sidebar search displays a matching list of recently viewed records.
Enable Single-Search-Result Shortcut for Sidebar and Advanced Search If this setting is enabled, users skip the search results page and go directly to the record's detail page when their search returns only a single item.

Number of Search Results Displayed Per Object - The Number of Search Results Displayed Per Object area allows you to configure the number of items that are returned for each object in the Search Results page.

Lookup Settings - The Lookup Settings area allows you to enable enhanced lookups and lookup auto-completion for enhanced lookup-enabled objects and any custom object lookups.
Picklist:

Values are static or nearly static
Values can be maintained by an administrator
All selectable values are displayed at once (drop down menu)
The total number of values is relatively low (I'd suggest a maximum of 100, but the actual limits are much higher)
You want to use controlling and dependent picklists (see Field Usage & Field Types) — this can be done to some extent with lookup filters (see Lookup Filters) and a little bit of creativity, but the net result isn't quite the same
The picklist value does not have any other associated data (e.g. the lead's favorite brand is Dell; no other information about Dell is needed)
Values do not need to be validated via the API (there is an AppExchange workaround to this, which I have not personally used)
Values are captured in web-to-lead submissions (web-to-lead does not support custom relationship fields).
You want to capture multiple values without creating multiple records (e.g. the lead's favorite brands are X, Y,Z; use a multi-select picklist instead of a many to many relationship)

Custom Object:

Values change frequently
Values can be added/changed by users
Selectable values can be searched for by users (lookup dialog box)
The total number of values is high
The value has associated data (e.g. the lead's favorite brand is Dell; Dell's address is X)
Values in this list are used in multiple references (e.g. the lead's favorite brand is Dell; a marketing campaign is sponsored by Dell as well)
Values need to be validated via the API (useful for integrations)
You want to use delegated administration (see Delegated Administration) on your custom object