Standard and Custom Objects

Question 1

Lookup Relationship

Answer 1

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 values in the list.

Question 2

Master-Detail Relationship

Answer 2

Creates a special type of parent-child relationship between this object (the child/detail) and another object (parent/master) where: relationship field is required on all detail records, 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 rollup summary fields on master record to summarize detail records.

Question 3

Standard Fields

Answer 3

Already exist on SF objects and offer limited customization, such as ‘Opportunity Name’ and ‘Amount’

Question 4

Custom Fields

Answer 4

Custom fields of data types, such as Picklists, can be created to store more data on objects.

Question 5

Changing Field Type

Answer 5

Field type of a custom field can be changed, but it can cause data loss, such as changing from Text to Number

Question 6

Deleting Fields

Answer 6

A custom field that is not referenced can be deleted if it is no longer required, but it also deletes the field data.

Standard fields cannot be deleted. Custom fields can be deleted but corresponding data will be deleted, and can’t be deleted if references somewhere else. Deleted fields can be restored within 15 days of deletion.

Question 7

Custom Objects

Answer 7

Custom objects can be created to store additional data in Salesforce when standard objects are not appropriate.

Created to record custom data not covered by standard objects. Up to 200 custom objects can be created in Enterprise and 2000 in Unlimited/Performance edition. Relationship fields can be used to define relationships between objects.

Question 8

Tabs

Answer 8

Used to allow access to custom objects, web pages, Visualforce pages, or Lightning pages

Question 9

Apps

Answer 9

Collection of tabs made visible in certain profiles. Custom apps can be created while standard apps already exist.

Question 10

Page Layouts

Answer 10

Control the layout and organization of fields, related lists, buttons, links, report charts, and other items on objects.

Question 11

Creating a Custom Field

Answer 11

Select Data Type > Enter Details (Description, Help Text Label, Picklist Values) > Set Field Level Security > Add to Page Layout

Question 12

Picklists

Answer 12

Standard or multi-select list using either custom defined values or values from a global value set. If global value set is used, picklist is restricted. Picklist values can be deactivated, which doesn’t affect existing values.

Question 13

Record ID Field

Answer 13

Globally unique read-only system type field assigned to every object in SF. IT is generated when the record is created, and every record has a 15-character case sensitive unique identifier. ID available in the URL.

Question 14

External IDs

Answer 14

Fields that contain a unique identifier from a system outside SF. There can be up to 25 external IDs on one object. Ex. Add SAP Account Number to Account object and mark it as an external ID.

Question 15

Rollup Summary Fields

Answer 15

Defined on the master object and available for certain object relationships such as Standard>Custom, Custom>Custom and certain standard relationships. Used to roll-up either the sum of the value of a particular field in the child object, return the min or max value, or count the number of records.

Question 16

Formula Fields

Answer 16

Read-only fields that automatically calculate a value based on other fields or a formula. Automatically updated when one of the fields used in the formula changes.

Question 17

When creating a custom object…

Answer 17

a new tab must be created to be able to create records via the user interface. Custom tabs can be custom object, web tabs, Visualforce tabs or Lightning tabs. Web tabs will embed a web page within a Salesforce tab.

Question 18

Record Types

Answer 18

Allow defining different picklist values, page layouts, and business processes on standard or custom objects for different profiles. Can be used when one object is used for different purposes and gathers different information e.g. internal and external cases, or if a company gathers different information on leads. Each object has a default record master record type that is hidden. Assigning a record type to a profile gives the user the ability to create records of that record type. Users can still see records of all record types.

Question 19

Business Processes

Answer 19

Associated with record types to define the lifecycle of leads, opportunities, cases, or solutions for different user profiles. Ability to set stage lists to route projects.

Question 20

Path

Answer 20

Created in Lightning Experience for custom objects and some standard objects to display their lifecycle based on a picklist field. Intended to capture the lifecycle of standard objects such as Leads, Campaigns, Accounts, Contacts and Cases and are used to guide users along steps in a process.

Question 21

Permission Sets

Answer 21

Ability to assign record types to a profile or individual.

Question 22

Page Layout Assignments

Answer 22

Specified for every record type, even when a record type is not available to that profile.

Question 23

Steps to Create a Record Type

Answer 23

1. Create page layouts to be used for record types. 2. Add any additional picklist values. 3. Create record type record. 4. Assign record type to profiles. 5. Assign page layout for each profile for each record type. 6. Select picklist values for record type.

Question 24

Business Processes

Answer 24

Capture the lifecycle of leads, opportunities, cases and solutions. Allow for different picklist values to be related to record types for sales, lead, support and solution processes.