Salesforce Admin Flashcards
(42 cards)
What is a is a Standard Object?
Objects store records, think of it as a ‘storage unit’ for records (Similar to Tabs in a spreadsheet; it has to do with an account or business): Container of sorts contained with specific properties and values depending on it’s use-case
You can connect a lead and an account, by creating relationships between standard and custom object to use that data and to view
What are types of Standard Object
Accounts:
Contacts
Leads:
Opportunities:
Cases:
Accounts
Accounts can be seen as a business or organization
They can also be people
An object type
You can connect a lead and an account, by creating relationships between standard and custom object to use that data and to view
Contacts
Are people
The majority of the time they are related to an account
an object
Leads
Someone/business that can be a potential sale or turn into an Opportunity
Type of contact that are usually involved in a business or sales process
an object
You can connect a lead and an account, by creating relationships between standard and custom object to use that data and to view
Opportunities
Last phase of the deal/sales
Related to Sales Processes
Due to the various stages and dollar amounts, it helps Sales people or people in fundraising so they know where should spend their time and effort
An Object
Cases
They help solve a problem or issue for customers, companies or organizations
Groups or individuals can work on this object to help customers on getting the support they need
an object
Data Model:
How many objects in your Salesforce org relate to one another
Schema Builder:
a visual representations that shows the relationship between various objects in your Salesforce org
Related records/related lists:
Appears on a page layout, either through a Master-Detail relationship or a look-up relationship
Records
(Row ↔️ specific details that are within a spreadsheet)
Opportunities are sale deals, it keeps a record/status update on what actions have taken place to close the deal
Field
(Column ↕️ like categories that can be filtered), you can add custom fields as well as standard field types
Look up Relationship:
Loose relationship between 2 objects (Can be deleted and the other one still exists)
Links 2 objects together, to see related items from one object to another
Used to relate one object to another object
Relationships can be a one to one, one to many, self, external, indirect or hierarchical relationship
Accounts & Contact, Accounts & Opportunities have a special type of look up relationship
If the parent record is deleted, the child record will be deleted too
Master Detail Relationship:
Example: Account and Opportunity
Close knit relationship (if one is deleted, all will be deleted)
Standard objects must be on the master side of the relationship
Child object inherits the security setting from the master object
Can be between 2 custom objects
Can be 1 to 1, 1 to many or many to many type of relationship
Roll-up Summary Field is only available to this relationship
Used to count child records and post that on the parent record. Sample: want to know the total dollar amount of all opportunities and then display that on the account record related to those opportunities
DIFFERENCE BETWEEN ROLL-UP SUMMARY FIELD & CROSS OBJECT FORMULA (depending on selection)
Roll Up - you count the child objects and present a value on the Parent object
Cross Object - you take a value that is displayed on the parent and displaying it on the child
Create Fields
In Set up: choose an object & field > new > choose Type of Field [Field label if it is not a relationship field]>Choose a field attribute [example: is the field required?what happens if its deleted>choose page layout>save
Edit / Customize Fields
Standard Fields cannot be deleted but they can be hidden from the Page layout or Renamed
Custom Fields can be added, deleted, renamed or changed to a different custom field entirely from the Page layout.
Edit the page layout(s) to remove the field or move it to a more appropriate place on the page layout
You may need different page layouts, if it should be seen sometimes but not others
Different Field Data Types: Can put on Standard & Custom Objects
Junction Objects (Many-to-Many Relationships)
Junction objects act like a mediator between 2 objects
Ex: Metro Junction - Many people use Bart as transportation, but mostly everyone has a different destination and have to transfer to different stations, those transfer stations work like a junction between origin and destination
Library is another example of a junction object
Page Layouts for Standard and Custom Objects
Can be assigned to profiles to control which fields, related lists and other items appear on records for different users
Understand the implications of deleting fields
All of the field history data is deleted and changes are no longer tracked, when a custom field is deleted. A background process periodically runs that cleans up metadata associated with deleted custom fields
Other database objects (forms) will not be able to use the query as a source of data from the deleted field
Field values should be archived before a field is deleted, it can be restored from the recycle bin within 15 days
Create and Assign Page Layouts
Page layout are assigned a record type & Profiles control record types
Page layouts control what a user with a specific profile can do & what fields or buttons are available
Users do not determine what’s on a page layout. Profiles determine what a user can do
Create and Assign Record Types
Setup> Quick Find “Record” >Record Types >New> Enter: Record Type Label, Record Type name, (both name and label can be the same) Description (whats it for), Check what profiles have control over the Record type> next>Select “page layouts”
Record Types: Allow defining different picklist values, page layouts and business processes on standard or custom objects for different profiles
Can be applied to any standard or custom object
All Records can be the same, but have different expectations of what fields would be filled out. Ex. Job applications, can be for the same company but different roles that need different fields that pertain to that role
Users don’t control record types, profiles control Record Types and Page Layouts
DO NOT USE RECORD TYPES FOR:
-Accounts > can use Child Objects instead
-Contacts
-Different values based on another field
-Use Dependent/Controlling Fields
Single page layout assigned per profile
-Use different Profile Page Layout Assignment
WHEN TO USE RECORD TYPES FOR:
- Different values based on profile/process
- Multiple page layouts assigned per profile (many leads)
- Record Type + Profile Page Layout Assignment