Apex Salesforce

SALESFORCE CRM BASICS

  What is Cloud Computing ?
Cloud Computing is a concept, which provides the various approaches, to access each
IT services over the internet by using any device, and by paying the rental amount to the
vendor.
By using Cloud Computing, we can access Servers, Storage, Databases, Networking,
Software, Analytics and more over the Internet (“the Cloud”).
Companies offering these computing services are called Cloud Providers. And charge
for cloud computing services based on usage, similar to how you are billed for water or
electricity at home.
Uses of Cloud Computing: By using Cloud Computing, we can achieve the below
services.
We can Build New Applications and Services We can Store, back up and recover data
No Upgradation cost.
No Pre-Requisite software’s to install
We can Host our own websites and blogs to the internet Stream audio and video
Deliver software on demand

Q : Benefits of Cloud Computing: Here are 6 common reasons organizations are
turning to cloud computing services.
Cost:
Cloud computing eliminates the capital expense of buying hardware and software and
setting up and running on-site datacenters.
Speed:
Most cloud computing services are provided self service and on demand, so even vast
amounts of computing resources can be provisioned in minutes.
Performance:
The biggest cloud computing services run on a worldwide network of secure datacenters,
which are regularly upgraded to the latest generation of fast and efficient computing
hardware.
Reliability:
Cloud computing makes data backup, disaster recovery and business continuity easier
and less expensive, because data can be mirrored at multiple redundant sites on the cloud
provider’s network.
Q : Classifications of Cloud Services:
Most cloud computing services fall into three broad categories. These are sometimes
called the cloud computing stack
Software As a Service (SAAS):
When the customers are accessing the "Readymade Applications" on rental basis, then it
is called as "Software As a Service".
Software-as-a-service (SaaS) is a method for delivering software applications over the
Internet, on demand and typically on a subscription basis.
Cloud providers host and manage the software application and underlying infrastructure
and handle any maintenance, like software upgrades.
Platform As a Service (PAAS):
When the customers are accessing the "Development Platform" on rental basis, then it is
called as "Platform as a service".
PAAS supply an on-demand environment for developing, testing, delivering and
managing software applications. PaaS is designed to make it easier for developers to
quickly create web or mobile apps, without worrying about setting up or managing the
underlying infrastructure of servers, storage, network and databases needed for
development.
Infrastructure As a Service(IAAS):
When the customers are accessing the "Server Resources (Memory, Performance,
Security)" on a rental basis, then it is called "Infrastructure as a service".
With IaaS, you rent IT infrastructure—servers and virtual machines (VMs), storage,
networks, operating systems—from a cloud provider on a pay-as-you-go basis.

 

 

Q : What is CRM Basics ?
CRM stands for Customer Relationship Management
A CRM system is an Application / Tool that allows you to manage all your customers,
partners and prospects information all in one place.
By using CRM applications, we can track the existing customer and new customers
information of an organization.
With the help of CRM, we can maintain a 360 degree view of your customer. (i.e. from
Capturing the customer to, till offering the services to the customer)
Q : What are the Benefits of using CRM Application ?
Improved customer relations Increase customer revenues Better internal communication
CRM Improves Your Customer Service Automation of Everyday Tasks Improved
Analytical Data and Reporting
Q : What is CRM Terminology / Vocabulary in Brief ?
Campaign:
It is a way to promote the organization products / services. We can use the other ways to
do the marketing like Conducting Stalls, Trade Shows, TV Advertisements, Theatre
Advertisements, Posters, Pamphlets, Banners, Hoardings, Digital Marketing, Email
Marketing, Tele Marketing, Free Samples, etc.
Lead:
Lead is nothing but a person or an Organization or a Business, who just showed interest
in your organization product or service.
Lead is also called as "Prospect" or "Potential Customer". Lead is not our customer.
By conducting the Campaigns we can capture one or more Leads. (i.e. Between
Campaign and Lead, we have One- Many association)
Account Record: It describes the basic details of the customer.
Ex: Customer Name, Rating, Industry, Type, Phone, Fax, Billing Address, Shipping
Address, active, Annualrevenue, etc.
Contact Record: It describes the Contact details of the customer. An account can be
associated with one or more contact records.
Ex: First Name, lastname, title, department, Birthdate, phone, fax, mobile, home phone,
other phone, email, mailing address, etc.
Opportunity Record: It describes, how much business we did with the customer. It
describes about the products purchased by the customer and revenue generated from the
customer.
Between Account and Opportunity, we have One-Many association. i.e. An Account
record can have one or more associated opportunities.
Case:
Case is nothing but the detailed information of the problem, which my customer is facing
with my product / service.
Between Account and the Case, we have One-Many association. i.e. A customer can raise
one or more cases / complaints.
Solutions:
Solution is nothing but the detailed information of the resolution of the case.
Q : What is Force.com Platform ?
Platform provides a set of resources, to build your custom application.
By using Force.com,
We can customize the existing salesforce CRM application.
We can leverage / extend the salesforce CRM functionalities, by adding the Additional
features based on the need.
We can build the custom application.
By using Force.com platform, we can build and deploy the next generation cloud
applications. Force.com Platform offers 2 Programming Languages as below.
Apex Programming:
It is a Cloud based Object Oriented programming, used to build the custom business logic
based on the need.
Visualforce Programming:
It is a web development framework, used to design attractive and dynamic user
interfaces.
By using the Force.com platform, we can integrate the integration of salesforce
applications with any third party external system.
Q: What is Database.com?
It is a customized database of Salesforce, where the actual objects and records will reside.
Which supports ORM Technology (Object Relationship & Mapping)
It ensures Data Security, by having the ISO 27001 & SAS 70 Type II Certifications.
Which are purely concentrating on "Information Security and Confidentiality".
Salesforce maintains a Disaster Recovery Center in each region (NA/EU/AP), to get back
the Data if any data loss due to some environmental issues.
All Salesforce implemented applications will use the "Database.com" as the Backend.
Salesforce Releases:
Salesforce keeps on providing the latest features as part of new releases. Salesforce
provides 3 releases per a year, which are seasonal basis.
Winter Release. Spring Release Summer Release
Each release contains the latest features associated with SAAS (Salesforce CRM), PAAS
(Force.com) and Infrastructure.
Salesforce provides the latest releases of salesforce features on Free of cost to all
customers. Each release name will be post-fixed with the Current Financial year number.
Spring '19 --> (Previous Release) Summer '19 --> (Current Release) Winter '20 -->
(Next Release)
Q : What is Multi-Tenant Architecture?
Multi-Tenant Architecture:
Salesforce supports MultiTenant Architecture, will allow sharing the Salesforce
resources to the multiple customers.
Salesforce provides the common infrastructure for a set of customers. They won't provide
a dedicated server for each customer.
MultiTenant Architecture allows the customers to access the resources on a rental basis.
Q : APPLICATIONS IN SALESFORCE ?
Application contains a set of Tabs, which provides a collection of user interfaces to
manage the application specific data. All the Tabs will be represented on the "TabBar".
By using these Tabs, we can perform all the DML operations on the Objects. (INSERT,
UPDATE, DELETE, UNDELETE) and View.
Salesforce provides 2 Types of Applications.
1. Standard Applications:
These are the readymade applications provided by salesforce by default as part of the
Salesforce CRM. (Ex: Sales, Service, Marketing, Content, Salesforce Chatter,
Site.com,... etc.)
By using these applications we can manage the existing and new customers information.
Note: We can customize or leverage the standard applications by adding the additional
enhancements. But, we can't remove the Standard Applications from the Organization.
2. Custom Applications:
The Administrator / Salesforce Developer can create their own custom applications based
on the need. (Ex: Banking, Finance, Insurance, HealthCare,...etc.)
Q : What are the OBJECTS in Salesforce ?
Salesforce provides a set of readymade objects by default as part of Salesforce CRM
Application. Object represents a "Table" in "Database.com". Database.com is a Cloud
Database used by salesforce by default. Which contains all the salesforce objects and
records inside it.
Ex: Campaign, Lead, Account, Contact, Opportunity, Case, Solution, Contract, Order,
Product, Feedback, Performance Cycle, ..etc
The user is able to manage the records inside the objects. i.e. The user can perform all the
DML manipulations inside those objects. (i.e. Insert, Update, Delete, Undelete) and View
records also. To manage the records inside the objects, salesforce provides a set of Tabs.
Q : What are TABS in SALESFORCE ?
Tab Provides a set of graphical user interfaces, by which we can manage the records
inside the associated object. By using Tab, we can insert, update, delete, view, Undelete
the records inside the object.
For each object, salesforce provides a separate Tab. Which is used to manage the records
inside the associated object.
An object can have only one Tab. (i.e. Object To Tab, we have one-one association)
All Tab Names will be represented with "Plural Names" as below.
Tab Name Object Name
Accounts Account
Contacts Contact
Opportunities Opportunity
Leads Lead
Campaigns Campaign
Cases Case
Positions Position
Customers Customer
Candidates Candidate
.... etc ... etc
Q : Creating a Custom Application .
The Administrator / Salesforce Developer can create their own custom applications based
on the need. Ex: Banking, Finance, Insurance, HealthCare,...etc.
Note: We can Customize / Leverage the Custom Applications based on the need. And we
can remove the custom application from the organization, if it no longer needed.
We can create our own Custom application with the below navigation.
Click on "Setup" menu.
Goto the "Build" menu in left panel. Click on "Create" and expand it.
Click on "Apps" link.
Click on "New" button, to create the New Application. Select the Option "Custom App"
and click on "Next" button. Enter the Application Label, Name and Description.
Click on "Next" button.
Select the Application Logo / Image, by using "Insert Image" button. Click on "Next"
button.
Select the Required Object Tabs, to be used inside the Application, by using "Add /
Remove"
Buttons.
Arrange the Tabs in the required order by using "Up / Down" Navigation button. Select
the Default Landing Tab from the Picklist.
Click on "Next" button.
Select the "Visible" checkbox, to make the application to be accessible to all users inside
the organization.
Click on "Save" button.
Q : HOW TO CREATE CUSTOM OBJECTS IN SALESFORCE .
Object Represents a Table, which can be used to store a collection of records inside it.
Objects are the Custom Tables, which can be used to store organization specific /
application specific data. All the objects in Salesforce will get resides in "Database.com".
Salesforce provides 2 types of Objects.
Standard Objects: These are the readymade objects provided by Salesforce by default,
which has been created upon Salesforce CRM application development.
Ex: Account, Contact, Opportunity, Campaign, Lead, Case, Solution, Order, Contract,
Forcast, Product, Pricebook, Performance Cycle, Goal, Metric, Feedback, etc.
Custom Objects: Salesforce allows us to create our own custom objects based on the
application requirement. Custom objects are database tables that allow you to store data
specific to your application in Salesforce.com. You can use custom objects to extend
Salesforce.com functionality or to build new application functionality.
Ex: Project c Table, Candidate c Table, Position c Table, etc.
Once you have created a custom object, you can create a custom tab, custom related lists,
reports, and dashboards for users to interact with the custom object data.
Allow Reports: This feature allows the user to generate the reports based on the data
exist in the object.
Allow Activities: This feature allows the user to Create the Tasks / Assigning the Task /
Generating the Events based on the Object Records.
Track Field History: This field allows the user to Track the Field History whenever any
of the person modified the record values. (To Track the values like.. Who modified the
record, when they modified the record, what field’s values modified, old value and new
values of the field etc.)
Allow in Chatter Groups: It allows us to include the field changes in the chatter feeds.
In Development: I the object’s Deployment status is “In Development”, this object
can’t be used by the other users.
Deployed: This object can be used by other users, in-order to create the records. i.e. It
is ready to use by the users.
Select the Check Box “Launch a New Custom Tab Wizard for the Custom Object”,
Which creates a new Tab for the object to manage the records (Insert / Update/
Delete/View).
Click on “Save & Next” button
Q : CREATING CUSTOM TABS IN SALESFORCE .
Tab provides a Graphical User Interface, by which the users / customers / partners /
employees can manage the records inside the object.
Upon creating a Custom object, if the user didn't select the last checkbox "Launch a New
Custom Tab Wizard After Saving the Custom Object", then Salesforce will not provide
the "Tab" for the object. We need to create the Tab for the object manually.
Custom Object Tabs: This feature is used to create a Tab to be used to manage the
records exist inside the object.
Web Tabs: These are used to re-direct the user to the specified URL / path of the
External Application upon click on the Tab.
Ex: Re-direct the user to "Office 365", Re-direct the User to "Weather Map Application",
etc...
Visualforce Tabs: By using this feature, we can re-direct the user to the specified
Visualfore page, Upon click on the Tab.
Lightning Page Tabs: By using this feature, we can re-direct the user to the specified
Lightning page, upon click on the "Tab".
Upon creating a custom object tab, we have to follow the below navigation
Click on "Setup" menu.
Goto the "Build" menu in left panel Click on "Create" option and expand it. Click on
"Tabs" link.
Goto "Custom Object Tabs" section.
Click on "New" button, to create a New Tab.
Select the Required Object Name from the Picklist, to create the Tab. Select the "Tab
Style", to be applied
Click on "Next" button. Make the Tab to be get visible for all the profile users. Click on
"Next" button. Click on "Save" button.
Q : DIFFERENCE BETWEEN STANDARD FIELDS vs CUSTOM FIELDS .
STANDARD FIELDS Vs. CUSTOM FIELDS
S.No STANDARD
FIELDS
CUSTO
M
FIELDS
1 These are the Readymade
fields provided by the
Salesforce by default Like Id,
Name, Owner, etc.
Based on the application requirement,
SalesforceDeveloper / Administrator can
create their own required fields inside the
object. Which are called asCustom Fields.
2 We can customize the
Standard Fields based on
the Need. But, we can’t
remove the standard fields
from the object.
We can customize / remove the custom
field, when it is no longer needed.
3 We can’t create any
more standard fields
inside the object.
We can create one or more custom
fields inside the object upon need.
1. In Free Developer Edition:
An object can have a max. of
500 Custom Fields.
2. Unlimited Edition: An object
can have a max. of 800 custom
fields.
4 Each standard Field
contains 2 properties.
1. Field Label: It represents
the Label / Static text to be
visible inside the user
interface.
2. Field Name: It represents
the actual column name inside
the table.
Each custom field contains 2 properties.
1. Field Label: It represents the Label /
Static text to be visible in the user
interface.
2. API Name: It represents the
actual column name in the table.
(API – Application Programming
interface)
5 Standard fields can be
available for both
Standard and Custom
objects.
Custom fields can be applicable for both
Standard and Custom objects.
6 Standard field’s Field Name
will look like normal words.
(Ex: ID, name, rating,
industry, type, etc.)
Custom field’s API Name will be
post-fixing with “ C” representing a
Custom Field.
Q : WHAT IS FIELD TYPES / DATA TYPES IN SALESFORCE ?
Creating the Fields are nothing but creating the columns inside the table. Upon creating
the Columns inside the Table, we need to specify what type of data can be held inside the
column. i.e. Upon creating the Field in an object, we need to select any of the data type as
below.
1. Auto Number :
This field type is used to make the column value auto generated. By using this
field type, we can generate the values for the field based on the specified format.
So, the Auto Number field is called a "System Generated Field". Auto
Number field will generate the value for the field upon saving the New record.
System Generated Fields are "Read-Only" fields.
2. Formula :
Allows users to automatically calculate values based on other values or fields such as
merge fields. 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 . Not available
for external objects.
Salesforce uses the round half up tie-breaking rule for numbers in formula fields. For
example, 12.345 becomes 12.35 and −12.345 becomes −12.35.
3. Roll-Up Summary :
Roll-Up Summary Fields in summarize data from a set of related detail records
and automatically display the output on the master record. These can be used to display
the sum, maximum, minimum value of a field in a related list, and also the count of all
the records listed in a related list. They are only available to master objects in a
master-detail relationship.
After creating a Roll Up Summary Field on an object, the master-detail relationship
cannot be converted into a lookup relationship.
4. Lookup Relationship :
Creates a relationship between two records so you can associate them with
each other. For example, opportunities have a lookup relationship with cases that
lets you associate a particular case with an opportunity.
On the parent record, you can display a related list to show all the records
that are linked to it. You can create lookup relationship fields that link to users,
standard objects, or custom objects. If a lookup field references a record that has
been deleted, Salesforce clears the value of the lookup field by default.
Alternatively, you can choose to prevent records from being deleted if they’re in a
lookup relationship.
5. Master-Detail Relationship :
Creates a relationship between records where the master record controls certain
behaviors of the detail record such as record deletion and security. Not available for
standard objects or external objects, although you can create a master-detail relationship
field on a custom object that links to a standard object.
Master-detail relationships can’t be used with campaign members.
6. Checkbox :
Allows users to check a box, indicating a true or false attribute of a record. When
using a checkbox field for a report or list view filter, use “True” for checked values and
“False” for unchecked values. The Data Import Wizard and the weekly export tool use
“1” for checked values and “0” for unchecked values.
7. Currency :
Allows users to enter a currency amount. The system automatically formats the field
as a currency amount. This formatting is useful if you export data to a spreadsheet
application. Not available for external objects.
8. Date :
Allows users to enter a date or pick a date from a popup calendar. In reports, you
can limit the data by specific dates using any custom date field.
9. Date/Time:
This field type is used to store both Date and Time stamp value inside the column.
Meeting Start Time, Meeting End Time, CreatedDate, LastModifiedDate, etc.
Ex: I have a meeting / Client Call : 08/13/2017 06.00 PM
10. Email:
Allows users to enter an email address of up to 80 characters, which is validated to
ensure proper format. If this field is specified for contacts or leads, users can choose the
address when clicking Send an Email.
You can't use custom email addresses for mass emails or list emails.
Emails sent to a record's custom email address fields aren't logged against that record.
11. Geolocation:
Allows users to specify a location by its latitude and longitude. Geolocation is a
compound field that counts toward your org’s limits as three custom fields: one for
latitude, one for longitude, and one for internal use. Not available for external objects.
12. Number:
Allows users to enter any number. This number is treated as a real number and any
leading zeros are removed.This field type is used to store numerical type value, which
includes both Integer and Decimal values also. Note: We can store an 18-digit number
inside the field.
13. Percent:
It will allow us to store the Numerical values, which will be stored by post-fixing
with the "%" symbol. It will allow us to store an 18-digit number, which can be either
Integer / Decimal value.
14. Phone :
This field is used to store the 10 digit phone numbers. Once the user enters the 10
digit phone number, then it will convert the phone number into US phone number format.
Ex: Contact Number : 9988776655 ---> Save --> Contact Number : (998) 877 - 6655
15. Picklist:
This control is used to store some set of values inside it, from which the user can
select only one item at a time.Lets users select a single value from a list that you define.
Available for external objects only with the cross-org adapter for Salesforce Connect.
16. Picklist-Multiselect:
By using this control, the user can select one or more elements from the collection
of elements.
Allows users to select more than one picklist value from a list that you define.
These fields display each value separated by a semicolon. Available for external objects
only with the cross-org adapter for Salesforce Connect.
17. Text:
Allows users to enter any combination of letters, numbers, or symbols. You can set
a maximum length, up to 255 characters.
18. Text Area:
Allows users to enter up to 255 characters that display on separate lines similar to
a Description field.
19. Text Area (Long):
Allows users to enter up to 131,072 characters that display on separate lines
similar to a Description field. You can set the length of this field type to a lower limit, if
desired. Any length from 256 to 131,072 characters is allowed.
The default is 32,768 characters.
20. Text Area (Rich):
This field allows us to enter the data in multiple lines upto max. of 1,31,072
characters. We can change the Font Color, Size, Style and we can include the images,
hyperlinks etc.
21. Text (Encrypted):
Allows users to enter any combination of letters, numbers, or symbols that are
stored in encrypted form. You can set a maximum length of up to 175 characters.
ou can archive, delete, and import your master encryption key. To enable master
encryption key management, contact Salesforce. Not available for external objects.
22. Time:
Allows users to enter a time of day, including hours, minutes, second, and
milliseconds.The time displays in a 12-hour notation with AM or PM. The displayed
time depends on the Locale setting on the Company Information page in Setup.
23. URL:
Allows users to enter up to 255 characters of any valid website address. Only the
first 50 characters are displayed on the record detail pages. When a user clicks the field
in Salesforce Classic, the URL opens in a separate browser window.
Q : EXPLAIN PAGE LAYOUTS IN SALESFORCE ?
Page Layout provides a set of graphical user interfaces, which allows us to interact with
the object. And we can perform all the DML manipulations (Insert, Update, Delete,
Undelete) And Retrieval on the object records.
Salesforce provides a Page Layout for each object by default. But, we can Create one or
more Page Layouts per an object based on the need.
Edit Mode/ Edit Page /Edit Layout:
Which displays the fields inside the object in "Editable" format. So, the user can create /
Update the existing record details.
Detail Mode / Detail Layout / Detail Page:
This Layout will display the detailed information of the record, which has been created /
edited by the user. Detailed page contains all the associated child records in terms of
"Related Lists".
Q: WHAT IS OBJECT RELATIONSHIPS IN SALESFORCE ?
Every application requires a Database, which stores the actual customer details / sales
details, etc.
Database contains a set of interrelated objects like Tables, Procedures, Cursors,
Functions, views etc. The data / records will get resides in a structured format by using
Tables.
We can have one or more tables in a database, where the actual records get resides.
We can store the data in a single table / in multiple tables.
All Salesforce objects will get resides in “Database.com”, which is a customized database
of Salesforce. While storing the data in a single table, it causes the below issues.
Number of columns in the Table is restricted to 1024. Redundancy (Duplicate data).
Performance issues (upon Updating, Insert).
To void the above issues, we have to use "Normalization" process, which allows us to
decompose the data into different table without any data loss. (i.e. We need to store the
records into different objects.)
While storing the records into different objects, both the objects should be associated
with each other. We can map the association between the objects by using "Relationship"
feature in Salesforce.
Salesforce provides 6 types of Relationships as below.
● Lookup Relationship
● External Object Lookup Relationship
● Master-detail Relationship
● Hierarchical Relationship
● Many To Many Relationship
● One-OneRelationship
To map the association, Salesforce provides a set of "Relationship field types" by default.
We have the below relationships in Salesforce.
➔ Lookup Relationship
➔ External Object Lookup Relationship
➔ Master-Detail Relationship.
➔ Hierarchical Relationship
Q: HOW TO CREATE LOOKUP RELATIONSHIP ?
Use case: Create the Lookup Relationship between Hiring Manager and Position Objects
and describe the observations.
Pre-requisite: We should have the below objects.
● HiringManager(HiringManager c)
● Position (Position c)
Identify the Parent and Child Objects:
● HiringManager: Parent Object
● Position : Child Object
Observations:
Lookup Relationship provides the One - Many associations among the two objects by
default. (I.e. One Parent and Many Childs.)
While creating the child record, the Lookup field is optional by default. (I.e. we may or
may not select the parent record.)
Re-Parenting Option is available by default in Lookup Relationship.(i.e. We can change
the parent of a child record.)
Upon deleting the Parent record, Child records will remain in the Child object. (I.e. Only
parent records will be removed. child records will exist as it is.)
We can make the Lookup Relationship field as Mandatory, by selecting the "Required"
checkbox upon creating the Relationship field.
If the Lookup field is Mandatory(Required checkbox selected), then When we try to
delete the parent record which is associated with the child records, Salesforce doesn't
allow us to delete the parent record until all the child records has been removed.
We can have max. of 40 Lookup relationships per an object. Both Parent record and child
record will have "owner fields".
Sharing settings and security settings will be independent of each other.
We can make a standard object as a child object with the custom object in Lookup
Relationship. We can't apply the Rollup Summary field on Lookup Relationship objects.
Q : HOW TO CREATE MASTER-DETAIL RELATIONSHIP ?
Use case: Create the Master-Detail Relationship between Position and Candidate Objects
and describe the observations.
Pre-requisite: We should have the below objects.
● Position (Position c)
● Candidate (Candidate C)
Identify the Parent and Child Objects:
● Position: Parent Object
● Candidate : Child Object
Observations:
Master-Detail association provides One - Many association between the objects by
default. (i.e. A Parent record can have zero or more child records)
We can't create the Master-Detail relationship between the objects, where the child object
contains the records.
Upon creating the child record, selecting the Parent record is Mandatory. (i.e. Lookup
field is a Required field)
Re-Parenting option is not available by default in Master-Detail association.
We need to enable it manually, by selecting the "Allow Re-Parenting" checkbox upon
creating the field.
An object can have max. of 2 Master-Detail relationship fields.
Parent record will have the "Owner" field and Child record will not have the "Owner"
field. (i.e Child record will be completely under the control of Parent record.)We can't
make a Standard object as the Child for a Custom object with Master-Detail association.
We can add Rollup Summary fields on the Parent object.
Q : DIFFERENCE BETWEEN LOOKUP RELATION AND MASTER-DETAIL
RELATIONSHIP
Lookup Relationship Master-Detail Relationship
1. Lookup field is not a required field 1. Lookup field is a mandatory field while
while creating the child record / creating the detailed record
detailed record.
2. When you delete the parent record, 2. When you delete the parent record,
child record will not be deleted(only the associated child records also get
parent record will removed) deleted
3. We can have max of 40 lookup 3. We can have max of 2 master-detail
relationships on an object relationships on an object.
4. Re-parenting option is available by 4. Re-parenting option is not available
default. by default.
5. Sharing Setting and Security
settings
5. Sharing Setting and Security settings
are not dependant on parent record are dependent on parent record
6. Rollup summary fields can’t be 6. We can create the Rollup summary
applicable. fields on Parent Object only.
7. Standard object can be the detail 7. Standard object can’t be detailed
object for a custom object . object for a Custom object.
8. Owner field is available on 8. Owner field is not available for
detailed record . detailed record.
9. We can create the lookup 9. We can’t create the masterrelationships
on an object, which detailed relationship on object,
is having the records . Which is having the records.
Q : Relationships among Standard Objects .
Salesforce provides a set of standard objects as part of the Salesforce CRM application.
All standard objects are associated by using either Lookup or Master-Detail.
Account and Contact:
Between Account and Contact, Salesforce provides the Lookup Relationship.
● Account --> Parent
● Contact --> Child
Account and Opportunity:
Between Account and Opportunity, Salesforce provides "Lookup" association.
● Account --> Parent
● Opportunity --> Child
We have a common field in Opportunity object , with the name "Account ID". Which
holds the Account Record Id to which the opportunity is associated?
Account and Case:
Between Account and Case objects, we have Lookup Relationships.
● Account --> Parent
● Case --> Child
We have a common field in Case object, with the name "AccountID". Which holds the
Account Record Id to which the Case is associated.
Once we map the association between the objects by using either Lookup or
Master-Detail, in future we can change the relationship type from Lookup to
Master-Detail and vice-versa.
Q: How to Convert Lookup Relationship To Master Detail ?
We can't apply the Master Detail Relationship on an Object, Which contains the pre
existing records. We can convert the Look Relationship to Master Detail with the below
steps.
We need to apply the Lookup Relationship between the Objects First. Map each child
record with the associated Parent record.
Change the Relationship Field Type to Master Detail.
Q : How to Convert Master Detail Relationship to Lookup ?
Converting the Master Detail Relationship to Lookup is straight Forward. We can change
the Master-Detail association to Lookup directly, just by changing the field type from
Master-Detail to Lookup type as below.
● Position --> Parent
● Candidate --> Child
Q: How to Create Many To Many Relationship ?
In few cases, we have to map Many to Many association between two objects, Which
provides One- Many association from both the sides.
Ex: We have Two Objects Author and Book.
UseCase: Create Many-Many association between Author and Book objects.
An Author can participate while preparing the Multiple books (i.e. One to Many from
Author To Book). A Book can be prepared by multiple Authors (i.e. One to Many
Association from Book to Author)
In Salesforce, we can't map Many-Many to association between two objects directly.
We need to achieve this feature, by creating a Junction object. Which associated with
both the Parents with Master-Detail association
Q : What is Lookup Filters Configuration ?
Once the association has been mapped between two objects, the user can select the Parent
Record by using the Lookup dialog upon creating a New Child record.
Lookup dialog will display all the parent records, So that the user can select only one
parent.
We can filter the records to be displayed in the Lookup dialog box by using "Lookup
Filters configurations".
i.e. We can prevent the Salesforce to populate all the parent records in the Lookup dialog
by adding the required filter conditions as below.
Q: Explain Rollup-Summary Field ?
It is a Read-only field, which displays on detailed page of the parent record
Rollup Summary field calculates the values from a set of related records available in the
details object / related list.
The Rollup Summary field will automatically calculate the result based on the updates
done in the related records.
Rollup Summary field can be created only on Master Table, which is in Master-Detail
Relationship. It can’t be applicable for Lookup relationships.
The Rollup Summary field generates the results by using "Aggregate Functions" as
below.
Count():
It returns an integer value, which indicates the Number of child records exist in the child
object for each parent record.
Sum():
This function is used to calculate the Sum value for all the child record's fields.
Max():
This function returns the Highest value from all the associated child records.
Min():
This function returns the Smallest value from all the associated child records.
Q : What Are Workflow Rules Explain In Details ?
Workflows are a fantastic way to automate certain business processes. You can create a
rule, and based on certain criteria that you set, Salesforce can do a number of things, like
send an email, create a task, or update a field.
Workflows are used to automate the organization's business processes. (i.e. instead of
performing all the operations manually, we can delegate a few operations to the
application, which can be performed by the system automatically by itself based on user
defined criteria).
By using workflows, we can execute a few actions based on user defined criteria /
Conditions automatically. Each workflow contains certain Evaluation Criteria
(Conditions) and Actions.
Evaluation Criteria for the Workflows:
● Created: Which fires the actions, upon creating a new record in the object.
● Created, Every Time it’s edited: It fires the actions, whenever a new record gets
created, and each time the record gets edited.
● Created, Anytime Edited meeting the Subsequent Criteria: Which will fire the
Actions, upon a New record is created or Modified the existing record and
meeting the user defined conditions.
Actions in Workflows:
1. Send Email Notification:
Using this action, we can send an Email Notification to one / more users by using
an Email Template.
2. Create a New Task / Assing a New task to a user. :
Using this action we can assign a New Task to the specified User.
3. Update a Field:
By using this action, we can update a field value with the specified text.
By using a "Field Update" action, we can update only one field.
To update the multiple field values, we need to add multiple Field Update actions.
4. Send an Outbound Message:
By using this action, we can send an XML based secured SOAP message to the
external system.
Types of Workflows:
We can fire the workflow actions in two ways as below.
Immediate Action Workflows: It fires the Actions immediately, as soon as the criteria
are met.
Time-Dependant Action Workflows: It executes the actions, after the spoecified time
interval is over.
In Time Dependent Action workflow, Actions will be placed in to the Workflow Queue
till the scheduled run time. Once the Scheduled Time interval is over, then it will execute
the action and it will remove from the Queue.
Q: Explain Process Builder ?
Salesforce process builder is a powerful tool you can use to automate business processes.
Process builder allows you to do more than a simple workflow would. It is a tool that
allows you to automate business processes using a graphical representation of your
process.
It has a simple interface that allows you to point and click to select objects and fields
while setting up immediate and time-based actions. It is like a workflow tool that helps
you easily automate your business processes by providing a powerful and user-friendly
visual representation of your process.
The Process Builder’s simple and powerful design allows you to customize the automated
process. Actions Available In Process BuilderThere are several different actions you can
trigger the process builder. These actions are:
Trigger Apex code:
You can use Salesforce process builder to invoke Apex code you have written within
Salesforce. Apex can be anything from custom logic to save a record to complex business
processes. To invoke an apex class in process builder we have to use
"@InvocableMethod" attribute.
Create a record:
This will allow you to create new records and set certain field values for the new record.
Email alerts:
In order to send an email from a process, you must create the email alert. To send an
email alert that email should be associated with the same object on which process is
started. Email template contains the standard text, list of recipients, and template
Trigger a flow:
You can launch a flow from your process to automate complex business processes.
Post to Chatter:
Process builder post to chatter action helps to post information to any user or group
chatter feed within Salesforce. The post will appear in the chatter field as if the person
who triggered the process had written it. You can reference groups or topics and add
merge fields.
Submit for approval:
Only the record that started the process will be submitted. You can’t submit any related
records for approval.
Update records:
Update one or more records that are related to the record that started the process. You can
update the record with manually entered values or by using the values from related
records. We can update records of parent or child whereas workflow only updates same
or parent object from the child.
Quick actions:
You must already have global actions or an object specific action created within
Salesforce to use these quick actions. You can then select to log a call, send an email, or
update a record.
Process:
This action will call one process to another process. For this action, you need to choose
the process type as it is invoked by another process.
Q : What are Validation Rules ?
Validation Rules are used to enforce the user to provide the proper entry of data in the
fields. i.e. Upon inserting a New record or upon updating an existing record, we need to
verify whether the user has entered the data in all mandatory fields or not.
And we need to verify whether the user has entered the data in the correct format or
not.By using Validation Rules, we can maintain the Accuracy and Quality of data inside
the application.
Validation Rules will fire, always Before Inserting the record or Before updating the
record into the object. We have 2 types of Validations as below.
1. Client Side Validations: Client represents a Browser. When the user validates the
Data at user interface level, then it is called as "Client Side Validations.
2. Server Side Validations: When the user validates the Data at Database level, then it is
called as "Server Side Validations".
Q : What Is Data Management (Data Loader) ?
Data Represents --> Records. (User, Profiles, Account Records, Product Records, etc.)
Data Migration: Migrating the records from one instance to another instance.
Code : Features implemented in salesforce
Ex: Applications, Objects, Tabs, Validation Rules, Workflow Rules, Apex Classes, VF
Pages, Triggers, etc... Code Migration: Deployment.
By using Page Layouts, we can insert / update / delete only one record at a time inside the
object.
To perform the operations on the Bulk records at a time, salesforce provides the "Data
Management" features. By which we can perform the Bulk Import / Export operations on
the bulk records at a time in SObjects.
Salesforce provides the below ways to manage the bulk records.
By using Apex Programming
By using Import Wizard
By using DataLoader Tool (On-Premise)
Third Party Tools:
● Workbench
● DataLoader.io
● DataLoader CliQ
● Aside.io
● Informatica Cloud
For Data Migration:
By using this Data Migration, we can perform Import and Export operations in
Salesforce. (i.e. We can insert, Update ,Delete, Retrieve the records from the object.)
1. Import Wizard:
It's an on- email feature given by salesforce to perform Only Import operations (insert
and Update). By using this feature, we can insert / update the records into the object like
Account, Contact,
Solutions, Campaign Member and all custom objects.
2. Data Loader :
Data Loader is an On-Premise Tool, provided by salesforce, to perform both Import and
Export operations in salesforce objects.(i.e. We need to install the DataLoader into our
local system)
By using DataLoader, we can perform Bulk Imports & Bulk Export operations on all
Standard and Custom objects in salesforce.
By using DataLoader, we can perform the below operations.
● Insert
● Update
● Delete
● Undelete
● Export
● Export All
● Upsert
● Hard Delete
3. Workbench:
Workbench is a web-based system that is used by Salesforce administrators (hence,
Workbench in Salesforce) and Salesforce developers of an organization which helps them
to communicate with the Salesforce for various information like Data insert, update,
delete and export.
Workbench also helps in retrieving data. Workbench in Salesforce is built using
JavaScript and PHP. This is an advanced tool and more than 5 million data can be
recorded. Data Loader is here for any Data Manipulations in Salesforce. For updating any
record using Data Loader, first export the file, then modify it into an excel file and load it.
● Insert
● Update
● Upsert
● Delete
● Undelete
● Purge - Permanently delete
● Export
● Export All
Q: What Is Security ?
Upon Creating a Salesforce account, it will reserve some amount of memory in the
Salesforce server. Based on the selected Country name in the registration form, it will
allocate the memory in the associated region’s available server.
Newly created Salesforce account is called as a Salesforce.com Organization (Simply:
Org)
Each Salesforce.com organization will be identified by using an unique identification
number called "Salesforce.com Organization Id".
In a single Salesforce instance (Ex: AP2 / AP3 / NA41/ etc.), it will allocate the memory
for 8000+ Salesforce.com organizations.
Each organization in the Salesforce instance will have access to the "Salesforce CRM"
application.
Salesforce maintains a Common Set of Standard Objects, for all the organizations in the
instance. i.e. Salesforce is not maintaining a separate set of objects for each organization.
If any of the organization people creates a New Account Record, then it will reside in the
Same "Account" table.
To Differentiate the Records between the Organizations, Salesforce includes a Field
called as "Organization ID", in each object. Which holds the Organization Id, along with
the account record.
If multiple users exist in an organization, then to differentiate the records between the
users inside the organization, Salesforce maintains a "UserID" field in each object. Which
contains the User Id of the Person, who creates the cord.
When the user makes a request to Salesforce server, then along with the request details, it
will forward the Currently Logged In user Id and Organization id also.
Q: What is Profile ?
It is a component, which contains a set of permissions to be assigned to one or more users
inside the organization.
Profile decides what operations the user can perform inside the Salesforce organization.
Upon creating a User record, we should assign a Profile mandatorily. (i.e. Profile is a
mandatory field, upon creating the User).
Each user should have only one profile. (i.e. User to Profile, we have 1-1 association)
But, a Profile can be assigned to one or more users in the organization. (i.e. Profile to
Users, we have One-Many association).
Salesforce provides 2 types of profiles as below.
1. Standard Profiles:
These are the readymade profiles, provided by Salesforce by default.
Ex: Authenticated Website Profile, Standard User Profile, Platform user profile,
ReadOnly profile, etc.
We can't modify all the options that exist inside the "Standard profile". We can
modify upto some extent.So, as a best practice. It is always recommended to create your
own custom profile, by cloning an existing one.
2. Custom Profiles:
The Developer / Administrator, can create their own profiles, by cloning an existing one.
Which can be assigned to one or more users.
We can't remove the Standard profiles from the Salesforce organization. But, we can
remove the custom profiles, if it is no longer needed. We can modify all the options exist
inside the "Custom profile".
These are the readymade profiles, provided by Salesforce by default.
Ex: Authenticated Website Profile, Standard User Profile, Platform user profile,
ReadOnly profile, etc.
Q : What Is Role Hierarchy ?
In every organization , it should have a set of designations which can be assigned to one
or more employees.
In the similar way, Salesforce provides a Role Hierarchy which can be configured based
on the organization structure and we can assign the roles to one or more users in the
organization.
By default, salesforce provides a set of Roles, which we can use to assign to the users. If
the existing Roles are not suitable, then we can set up our own role hierarchy.
Q: What Is Organization Wide Defaults (Owd) ?
OWD Provides baseline level of access to all users in the organization on each object in
Salesforce.
OWD will be used to grant Record Level Access to the users inside the organization.
OWD can be assigned to both Standard and Custom objects in Salesforce.
OWD can be applicable on "Object" level. For each object we can assign a different
OWD option.
OWD will make the visibility of the records to the users based on "Role Hierarchy"(i.e.
OWD is Depends on "Role Hierarchy")
Salesforce provides the Below OWD Options..
● Private
● Public ReadOnly
● Public Read/Write
● Public Read/Write/Transfer
● Public FullAccess
● View Only
● No Access
● Use
● Controlled By Parent

 

Q: What is Role Hierarchy ?
A role hierarchy represents a level of data access that a user or group of users needs. The
role hierarchy ensures that managers always have access to the same data as their
employees, regardless of the organization-wide default settings. Role hierarchies don't
have to match your organization chart exactly. Instead, each role in the hierarchy should
represent a level of data access that a user or group of users needs.
Modeling the role hierarchy begins with understanding how the organization is
structured. This is usually built from understanding a manager’s scope, starting from the
top. The CEO oversees the entire company. The CEO usually has direct reports that can
then be segmented by Business Unit
That person then has direct reports that could be further segmented, and so on. Although
this sounds very much like an HR organizational chart, when modeling data access, focus
on data accessibility with a consideration to HR reporting.
Q : What is Auto sharing (Sharing rules) ?
Sharing Rules are used to open up the access to Salesforce Record on top of
OWD and Role Hierarchy. Sharing rules only work if the OWD for the record is either
Private or Public Read Only for any ( Default Internal or Default External ). When
Sharing Rule is executed and open up access to any record. Behind the scenes,
salesforce creates the record for Share Object. Share Object gets available for the
object if the OWD is Private or Public Read Only. We can not share the Records with
the user directly using Sharing Rules. But as a workaround, We can create a Public
Group, add the user to the Public group and share the records with that public
group.

Q: What is Manual Sharing ?
Manual Sharing is the most effective way to share a record with an individual without
disclosing the entire database. The user might belong to a different class and you can’t
classify his profile under a specific category. Also, Manual Sharing supports sharing data
with a group of users in the organization. Salesforce Admin can easily proceed with it
through the “Share” button present on the record itself.
Manual Sharing is important because it allows you to share records with users who
don’t have alternate access to it. However, the following users are eligible to further share
the records

 

Q: What Are Assignment Rules ?
Assigning the Lead/ Case records to either a User / Queue is a difficult process, when we
have more records. Which is a time consuming process.
To avoid this problem, we can make this process automated by using Assignment Rules.
Assignment Rules are used to assign a Lead / Case record to either a User / Queue based
on the user defined conditions.
i.e. We can transfer the ownership of the record to the specified user or queue
dynamically at runtime, instead of assigning the record to the currently logged-in user by
default.
Lead Assignment Rules:
By using Lead Assignment Rules, we can assign a Lead Record to either a User or Queue
dynamically at runtime, based on the user defined conditions.
Ex:Lead : City = 'Hyderabad' --> Hyderabad Queue Lead : City = 'Mumbai' --> Mumbai
Queue

 

Q: What are Permission sets ?
Permission Set’s are used to grant the additional permissions to one or more users in the
organization.
By using Permission set we can grant the similar access like Profile, but except the Login
IP Ranges and Login Hours.
Permission Sets will override the "Profile level permissions". ( i.e. We can extend the
Profile level permissions using Permission Sets.)
We can have one or more permission sets in an organization.