Object Manager and Lightning App Builder Flashcards
1
Q
Standard Objects
A
- Objects included with a SF org automatically
- These type of objects can be hidden, but they CANNOT be deleted
- Can have a relationship to other ________ objects
- Can also have a relationship to custom objects
2
Q
8 Examples of SF Standard Objects
A
1.) Account
2.) Contact
3.) Lead
4.) Campaign
5.) Opportunity
6.) Case
7.) Solution
8.) User
3
Q
Account
A
- SF standard object which is used to store information about companies and individuals (person accounts)
- Can be renamed to ‘Customers’ for example
- This is the parent object of Contact, Opportunity, and Case
4
Q
Contact
A
SF standard object which represents an individual associated with an account
5
Q
Lead
A
- SF standard object which is a prospect that can be converted into an Account, Contact, and Opportunity
- Can be converted into an Account, Contact, and (optionally) an Opportunity
6
Q
Campaign
A
- SF standard object which is used to store information about a marketing effort, such as a seminar
- Can have many members
- This object can be related to either a Lead or a Contact
7
Q
Opportunity
A
SF standard object which is used to store information about and track sales deals in progress
8
Q
Case
A
- SF standard object which can be used to store customers’ questions, feedback, or issues
- Web-to-Case or E-mail-to-Case can be used to create cases from customer-logged issues
9
Q
Solution
A
SF standard object which represents the description of a customer’s issue and its resolution
10
Q
User
A
SF standard object which is a record created to allow a person to log into SF and access information
11
Q
Custom Objects
A
- Created by the Admin to meet a specific use case
- Can be created to record custom data not covered by standard objects (common example is Expenses)
- Contains standard fields and may have custom fields added
- Ex: Job Candidate, Application, Position
- Note: ‘Name’ field MUST be configured (either Text or Auto-Number)
12
Q
Relationship Fields
A
Can be used to define relationships between objects
13
Q
3 Relationship Types in SF
A
1.) Standard Objects and Custom Objects
2.) Between 2 Custom Objects
3.) Between 2 Standard Objects
14
Q
Master-Detail Relationship
A
- A TIGHT relationship which relates 2 objects through a parent-child relationship
- Ex: Relationship between Account and Opportunity (an Opportunity must ALWAYS be associated with an Account)
- Can be one-to-one, one-to-many, or many-to-many
- Allows 1 object to be related to another in a one-to-many relationship
- This is a REQUIRED field, as all child objects (the object with the lookup) MUST have a parent (the record the User is looking up)
- Ex: An Opportunity must ALWAYS be related to an Account
- Therefore, if a Master record is deleted, ALL of the detail records are deleted as well (Exception: The ‘Allow Reparenting’ setting is enabled, which allows detail records to be associated with another master record when a master record is deleted)
- The child object (the one with the lookup) inherits the sharing and security settings of the parent object and has no settings of its own
- Standard objects MUST be on the master side of the relationship with a custom object
- Therefore, I CANNOT create a custom object and make it the parent of a standard object
- May also be between any custom objects
15
Q
Lookup Relationship
A
- A LOOSE relationship between objects (allows independent record ownership)
- Ex: Relationship between Accounts and Cases
- Links objects together so Users can see related items from 1 object on another
- Can be one-to-one, one-to-many, self, external (parent external object), indirect (child external object), or hierarchical (User object only)
- A self relationship can be created by creating this type of relationship to the same object (ex: An Account with this type of relationship to another Account field)
- Does NOT inherit the sharing and security settings from another object
16
Q
Many-to-Many Relationship
A
- Allows 2 objects to be related to each other when a record from 1 object can be linked to multiple records from another object and vice versa
- Are implemented via the use of a Junction object (an object which sits between the other 2 objects and has a master-detail relationship with both)
- Ex: If there is a ‘Position’ object and a ‘Candidate’ object, one position can be related to multiple candidates and a candidate can be related to multiple positions
17
Q
Hierarchical Relationship
A
- Relationship which allows Users to click a lookup icon and select another User from a pop-up list
- ONLY available on the User object
18
Q
Schema Builder
A
Can be used to view the data model as well as create objects, fields, and relationships quickly
19
Q
Record Types
A
These can be used to:
1.) Display different picklist values for the same field depending on the type
2.) Display different fields in page layouts based on a combination of the ______ type and User Profile
3.) Support different business processes for a given object
- Each object has a ‘Master’ ______ type that is system created (Note: If a ‘Master’ ______ type is selected, custom ______ types CANNOT be included
- All other manually-created ______ types are considered ‘Custom’ ______ types
- Note: If a Custom ______ type is selected, multiple custom ______ types can be included but NOT the Master ______ type
- Access is defined at the Profile level or through Permission Sets, or a combination of both
- Permission sets can ONLY grant access to Custom ______ types
- This type of access controls record creation and editing of specific types
- Users can view records of any ______ type, as long as they have access to the object
- Assignment specifies which ______ types a User can use when creating or editing records. Any User can view records with that ______ type, even if it’s not assigned to them
- Assignment does NOT have an impact on Users’ sharing settings
20
Q
8 Data Model Customization and Implications in SF
A
1.) Standard Fields
2.) Custom Fields
3.) Changing Field Type
4.) Deleting Fields
5.) Custom Objects
6.) Tabs
7.) Apps
8.) Page Layouts
21
Q
Standard Fields
A
- These type of fields already exist on SF objects and are used for recording common business details
- CANNOT be deleted
- Field labels can be changed
- Standard picklist values can be added, renamed, reordered, deleted, or deactivated
- Field History Tracking can be set
- Field-level help can be added
- Lookup filters can be added or edited
- Auto-number field format can be adjusted
- Can be removed from page layouts to hide them from Users
22
Q
Custom Fields
A
- ______ fields of data types, such as Picklist, External ID, and Roll-Up Summary, can be created to store more data on objects
- CAN be deleted (the data contained in the field will also be deleted)
- CANNOT be deleted though if it is referenced elsewhere in the application (ex: field updates in a Workflow or Process Builder)
- Can be created on standard and custom objects to store additional data
- Data types can be set according to the requirement
- This type of field can be set to required, which will require a value in the field before saving
- This type of field can be set as unique, which will prevent duplicate field values
- This field type can have a default value set. These include:
1.) Checkbox
2.) Currency
3.) Date
4.) Date/Time
5.) E-mail
6.) Number
7.) Percent
8.) Phone
9.) Picklist
10.) Text
11.) TextArea
12.) URL - These types of fields an be set as case sensitive so that values, such as ‘abc’ and ‘ABC’, are treated as different values
23
Q
Changing Field Type
A
The _________ of a custom field can be changed, but it can cause data loss, such as changing from Text to Number
24
Q
Deleting Fields
A
A custom field that is not referenced can be _______ if it is no longer required, but it also _______ the field data
25
Custom Objects
These types of objects can be created to store additional data in SF when standard objects aren't appropriate
26
Time Fields
- This type of field can be used to track time that is not specific to a single date, such as preferred contact hours
- It is useful for time management, event planning, and project management
27
Tabs
These can be added to to custom objects, custom apps, web pages, Visualforce pages, or Lightning pages
28
Apps
- This is a collection of tabs made visible to certain Profiles
- Custom ____ can be created, while standard ____ already exist
- 4 types:
1.) Standard Apps
2.) Custom Apps
3.) Profiles
4.) Default Tab
29
Standard Apps
SF comes with these types of apps automatically (ex: Sales, Service, Marketing)
30
Custom Apps
- Apps that are created
- The header can be customized for company branding
31
Profiles
Can have access to multiple sets and the default app can be set
32
Default Tab
Can be set for each app
33
Page Layouts
- Controls the layout and organization of fields, related lists, buttons, links, report charts, and other items on objects
- Fields can be added and removed from these
- Allows fields to be marked as read-only or required
34
Mini-Page Layout
Layout which controls the fields that are displayed when hovering over a record
35
4 Steps to Creating Custom Fields
1.) Select Data Type
2.) Enter Details
3.) Set Field-Level Security
4.) Add Custom Field(s) to Page Layouts
36
Picklists
- Type of field; Predefined list of values where Users can select from
- These are a great way to standardize data!
- Multi-select allow multiple values to be selected
- If a Global Value Set is used, then the picklist is restricted
- These can use custom defined values or values from a Global Value set
- If a value is imported into this and it doesn't exist and is not restricted, then this will be added
- A value can be deactivated (this will not affect existing values)
- A restricted ________ means that only the values defined can be used
- Other values cannot be inserted even via the API
37
Picklist Dependency
- Feature where an Admin can control which values can be selected from a picklist that are dependent upon the value selected in another picklist or a checkbox field
- Can be multi-select
38
Multi-Select Picklists
Can ONLY be a dependent field
39
Dependent Picklist
- Used to limit the available values on a certain picklist field depending on the values selected in another field
- CAN be multi-select
- Allows the values in one picklist to be filtered by the values in another picklist or checkbox field
40
Controlling Field
The picklist or checkbox that drives the filtering
41
Standard Picklist Fields
Can be controlling fields but NOT dependent fields
42
Custom Object Picklist Fields
CAN be controlling OR dependent
43
Roll-Up Summary Fields
- Fields which are used to aggregate data from child records, either as a SUM, a maximum of a numeric value or date value, a minimum of a numeric or date value, or a count of records
- Used to "roll-up" either the sum of the value of a particular field in the child object, and return the minimum or maximum value or a count of the number of records
- This can ONLY be created where the related Child object has a Master-Detail relationship with the Parent
- Defined on the Master object and available for certain object relationships such as Standard > Custom, Custom > Custom, and certain standard relationships
- Calculating this field's values may take up to 30 minutes, depending on the number of records affected and other factors
- It can be performed manually by selecting the 'Force a mass recalculation on this field' option on the edit page of the field
44
Dependent Field
The picklist that has its values filtered by the value selected in the controlling field
45
Formula Fields
- Read-only fields that allow an Admin to automatically calculate a value based on other fields or a formula, display a value, or use a value from a related object
- Automatically updated when one of the fields is used in the formula changes
- Can be based on a simple or advanced formula
- Merge fields can reference fields in related objects (ex: A custom _________ on Contact can reference a field from Account)
46
Simple Formula
Formula type which allows selection of fields from the same object and use of operators
47
Advanced Formula
- Formula type which allow selection of fields from the parent object and use of functions
- Also allows the use of merge fields, operators, and a range of functions to define the formula
48
Cross-Object Formula
Formula which references merge fields on related objects for calculations that will be displayed on detail pages, list views, and reports
49
7 Types of Formula Fields
1.) Checkbox
2.) Data
3.) Number
4.) Text
5.) Currency
6.) Data/Time
7.) Percent
50
Record Name
- MUST be configured when creating a new object. It's a way to identify records
- Can be a text field
- It can also be auto-number if it makes sense to have an auto-generated sequential record number
- This appears in Page Layouts, List Views, Related Lists, Lookups, and Search Results
51
Page Layouts
- Controls the layout and organization of fields, buttons, links, publisher actions, report charts, Visualforce, and related lists
- Allows fields to be marked as read-only or required
- Sections can be used to organize fields on the page
- Different ____________ can be assigned to different Profiles so that each type of User can see fields that are relevant
52
Deleting Fields
- Counts against custom field allocation within 15 days after deletion
- Hard-deletion of deleted custom fields can be accelerated in order to free up custom field allocation
- If a field is restored, it needs to be manually added back to page layouts and marked as required/unique again if needed
- After a field is restored, field history is available again
- If the field was part of a master-detail relationship, it will be restored as a lookup
- It needs to be converted to Master-Detail
53
Record ID Field
- A globally unique read-only system type field assigned to every object in Salesforce
- This is generated when the record is created
- Every record has its own 15-character case-sensitive unique identifier
- The API defaults to using 18-character case-insensitive record IDs
- This field is not displayed on the record detail page, but the ID can be found in the URL
54
External ID's
- Fields that contain a unique identifier from a system outside of Salesforce which can be used for matching records when data is imported or integrated
- There can be up to 25 of these types of IDs on an object
- For example, the ‘SAP Account Number’ field can be added to the Account object and mark it as an external ID. When data is imported or integrated into the Account object, records can be matched using the ‘SAP Account Number’ field instead of the record ID
55
Allow Reports
Option which allows an object to be reported on
56
Track Field History
- Option which allows the selection of fields for tracking field history on a record related list
- For custom objects, up to 20 fields may be chosen to track
57
Allow Activities
- Option which allows Activities (tasks and events) to be associated with the custom object
- The 'Open Activities' and 'Activity History' related lists need to be added to the page layout
58
Allow in Chatter Groups
- When enabled, this option allow Users to add the custom object records in Chatter groups
- The ‘Group record’ related list will display the records in the group detail page
59
Page Layouts
- Can be assigned to Profiles to control which fields, related lists, and other items appear on records for different Users
- Helpful if, for exmaple I would like an Admin Profile to show a number of audit fields while hiding these from my business Users
60
Business Processes
Can be associated with record types to define the lifecycle of Leads, Opportunities, Cases, or Solutions for different User Profiles
61
Record Types
- Allows different picklist values, page layouts, and business processes to be defined for a standard or custom object
- These can be used on a case object, which is when 1 object is used for different purposes and gathers different information (ex: internal and external cases)
- These can be used on Lead Objects. If a company gathers different information on leads, depending on if they are interested in a product or service
- These can be used for Master ___________ (each object has a system-generated Master __________ that is hidden
- Ex: When I have 2 completely different sales processes which require different information to be captured
- Multiple ____________ can be created on each object (but at the same time, I should make sure I have a legitimate business case to create multiple __________, as this can lead to a large administrative overhead if I have 10 - 20 of these)
- This is assigned 1 page layout type per Profile
- Assigning this to a Profile gives the User the ability to create records of that ____________. User can still see records of all ________, but they're only able to create ________ for ones which are assigned to them
- Can be assigned to a Profile or individual Users through Permission Sets
- Assignment specifies that the User can use that _________ when creating or editing a record
- Users can view records assigned to any ____________
- Page layout assignments are specified in Profiles ONLY
- When a Permission Set specifies a custom ____________, the User(s) assigned with that Permission Set gets the page layout that is specified for that ____________ within their Profile
62
Default Record Type
- Used when a User does NOT select the _________ (ex: Data Import, Lead Coversion, Flow)
- Set at the Profile level, and is selected when creating a new record (but can be changed)
- If there is only 1 active ____________, it is automatically selected
- A User can set this in their personal settings, so they are not prompted to select one when creating a new record
- This option is only available when there are 2 or more active assigned __________ on the User Profile
63
Path
- 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
- This can be created in Lightning Experience for custom objects and some standard objects to display their lifecycle based on a picklist field
- This can be created for custom objects and certain standard objects in Lightning Experience ONLY
- Similar to the visual guidance of moving through the stages that exists by default for Opportunity records in Lightning
- If a step has dependent fields, ALL dependent fields can be updated when updating a record from this
- For each stage, guidance and up to 5 fields can be displayed
- To enable and create this, search for 'Path Settings' from Setup
- When created, this will appear as a Lightning Component to be placed on the page
64
6 Steps to creating a Record Type
1.) Create page layouts to be used
2.) Add any additional picklist values
3.) Create ________ record
4.) Assign __________ to Profiles
5.) Assign page layout for each Profile for each ________
6.) Select picklist values for ________
65
Business Process
- Captures the lifecycle of Leads, Opportunities, Cases, or Solutions
- It references a standard picklist field and the values CAN be customized
- These allow for different picklist values to be related to record types for Sales, Lead, Support, and Solution processes
- For example, there may be 3 divisions, with 2 using the same Sales process, and another using their own Sales process. 2 of these can be set up and related to 3 record types for each division. Without this, the same set of picklist values would need to be maintained for each record type that uses the same set of values. These help streamline activity
- Can be set up within SF
- These can be used to align with the org's existing processes
66
Lead Processes
Defines different picklist values for Lead status
67
Support Processes
Defines different picklist values for Case status
68
Sales Processes
Defines different picklist values for Opportunity stage
69
Solution Processes
Defines different picklist values for Solution status
70
4 Objects where the Business Process must be created FIRST before the Record Type
1.) Opportunities
2.) Cases
3.) Leads
4.) Solutions
71
4 Things that can be customized for Standard Fields
1.) Field Labels
2.) Field Help
3.) Picklist Values
4.) Auto-Number Formatting
72
5 Main Custom Field Attributes
1.) Field Type
2.) Default Value
3.) Required
4.) Unique
5.) Case Sensitive
73
Self Relationship
A lookup to a different record of the same object
