🌩️ Salesforce Basics 1

🧭 1. Salesforce Clouds Overview

Salesforce provides different Clouds (modules) designed for various business processes. Each cloud
contains specific features and objects that cater to particular organizational needs.

1.1 Sales Cloud

●​ Purpose: Manage the end-to-end sales process.​

●​ Key Features:​

ELEARNING IT
○​ Lead & Opportunity Management​

○​ Account & Contact Management​

○​ Forecasting and Pipeline Tracking​

○​ Reports and Dashboards​

○​ Einstein Lead Scoring​

●​ Use Case: Used by sales teams to track leads, deals, and sales performance.​

1.2 Service Cloud

●​ Purpose: Enhances customer service and support.​

●​ Key Features:​

○​ Case Management​
 ○​ Service Console​

○​ Knowledge Base​

○​ Omni-Channel Routing​

○​ CTI (Computer Telephony Integration)​

●​ Use Case: Customer support centers and service departments.​

1.3 Marketing Cloud

●​ Purpose: Automates marketing campaigns and customer journeys.​

●​ Key Features:​

ELEARNING IT
○​ Email Studio, Journey Builder, Advertising Studio​

○​ Campaign Management​

○​ Customer Segmentation​

●​ Use Case: Digital marketing, email campaigns, and audience engagement.​

1.4 Experience (Community) Cloud

●​ Purpose: Builds branded portals for customers, partners, and employees.​

●​ Key Features:​

○​ Community Builder​

○​ Knowledge Sharing​
 ○​ Partner Relationship Management​

●​ Use Case: Customer self-service portals, partner portals.​

1.5 Commerce Cloud

●​ Purpose: Manages online commerce operations (B2B/B2C).​

●​ Key Features:​

○​ Product Catalog & Order Management​

○​ AI-Powered Personalization​

●​ Use Case: Online store solutions.​

ELEARNING IT
1.6 Other Popular Clouds

Cloud Description

Health Cloud Patient and care coordination management

Financial Services Banking, wealth, and insurance customer

Cloud management

Nonprofit Cloud Donor and fundraising management

Education Cloud Student and course management for

institutions
 🧱 2. Salesforce Objects
2.1 Definition

An Object in Salesforce is like a database table that stores data. Each record is a row, and each field is
a column.

2.2 Types of Objects

Type Description Example

Standard Provided by Salesforce Account, Contact,

Objects Opportunity

ELEARNING IT
Custom Created by users or Invoice__c, Project__c
Objects admins

External Data from external ERP_Order__x

Objects sources

Big Objects Stores massive data Event_Log__b

volumes

2.3 Key Object Features

●​ Fields​

●​ Record Types​

●​ Page Layouts​
 ●​ Validation Rules​

●​ Triggers / Workflows​

●​ List Views​

🧩 3. Salesforce Fields
3.1 Definition

Fields are data columns that store specific information within an object.

3.2 Common Field Types

ELEARNING IT
Field Type Description Example

Text / Text Area Stores text Name, City

values

Number / Currency / Stores numeric Amount, Price

Percent values

Date / DateTime Tracks dates and CreatedDate

times

Picklist / Multi-select Dropdown values Stage, Status

Checkbox True/False Active

 Formula Dynamic Total_Price__c = Qty
calculation * Rate

Lookup / Master-Detail Relationship AccountId, ContactId

fields

3.3 Field-Level Security (FLS)

Controls field access for different profiles or permission sets.

●​ Visible: Users can see the field.​

●​ Read-Only: Users can view but not edit.​

ELEARNING IT
●​ Hidden: Users cannot view or edit.​

🧰 4. Salesforce Apps
4.1 Definition

An App is a collection of tabs, objects, and functionalities grouped to serve a business purpose.

4.2 Types of Apps

Type Description

Standard Pre-built (Sales, Service, Marketing)

App
 Custom Created by admins or developers
App

Connected Integrates Salesforce with external

App systems via API

4.3 Components

●​ Tabs​

●​ Objects​

●​ Visualforce / Lightning Pages​

ELEARNING IT
●​ Navigation Bar​

🔗 5. Relationships in Salesforce
Relationships connect records between objects, similar to joins in databases.

5.1 Types of Relationships

Relationship Type Description Example

Lookup Relationship Loose link between objects Contact →

Account

Master-Detail Strong dependency; child deleted Invoice Line →

Relationship with parent Invoice
 Many-to-Many Created via a junction object Course ↔ Student
Relationship

Hierarchical Special for User object only Manager ↔

Relationship Employee

5.2 Key Differences

Behavior Master-Detail Lookup

Ownership Parent controls Independent

ELEARNING IT
Cascade
Delete
Yes Optional

Roll-Up Allowed Not Allowed

Summary

Security Inherited from Independent

parent

🧮 6. Formula Fields
6.1 Definition

Formula Fields automatically calculate values using expressions or logic and display read-only results.

6.2 Characteristics
 ●​ Read-only (calculated dynamically)​

●​ Updated automatically​

●​ Can reference fields, functions, and operators​

6.3 Example Formulas

Formula Description

TODAY() - CreatedDate Number of days since record creation

IF(StageName = "Closed Won", Show Amount only if Opportunity is

Amount, 0) Closed Won

ELEARNING IT
TEXT(Industry) & " - " &
AccountNumber
Combine text fields

6.4 Limitations

●​ Cannot trigger workflow actions.​

●​ Cannot reference long text areas directly.​

●​ Character limit ~3900 characters.​

✅ 7. Validation Rules
7.1 Definition

Validation Rules enforce data quality and integrity by preventing users from saving invalid records.
 7.2 Components

●​ Formula Expression: Must evaluate to TRUE for an error.​

●​ Error Message: Informs the user of the issue.​

7.3 Example

AND(

ISPICKVAL(Status, "Closed"),

ISBLANK(Closed_Date__c)

ELEARNING IT
Purpose: Ensures “Closed Date” is filled when a record’s status is “Closed”.

7.4 Best Practices

●​ Write clear, user-friendly error messages.​

●​ Keep logic simple.​

●​ Test thoroughly before deployment.​

📊 8. Roll-Up Summary Fields

8.1 Definition

A Roll-Up Summary field aggregates data from child records (in a master-detail relationship) into the
parent record.

8.2 Supported Functions

 Function Description

COUNT Number of related records

SUM Total of numeric fields

MIN Minimum value

MAX Maximum value

8.3 Example

ELEARNING IT
Parent Child Object Example Summary
Object

Account Opportunity Total Opportunity

Amount (SUM)

Project Task Count of Completed

Tasks (COUNT)

8.4 Limitations

●​ Works only with Master-Detail relationships.​

●​ Not available for Lookup relationships.​

●​ Limited number of roll-ups per object (usually 25).​

🔒 9. Security Connection with These Features
Security Feature Description Example

Org-Wide Defines baseline record Private, Public

Defaults access Read/Write
(OWD)

Profiles Define object & field CRUD access for Leads

permissions

Permission Sets Grant additional permissions Read/Write on Custom

Object

ELEARNING IT
Field-Level
Security

Sharing Rules
Control visibility of fields

Share specific records

Hide Salary field for
standard users

Share Accounts with

based on conditions Region = “West”

Manual Sharing User-driven sharing Record Owner manually

shares

🧠 10. Example Scenarios

Scenario Solution
 Calculate total invoice amount Formula Field or Roll-Up
Summary

Prevent closing a case without a Validation Rule

reason

Link Project with Account Lookup Relationship

Display only approved projects List View or Record Type

Show total number of tasks on Roll-Up Summary Field

Account

ELEARNING
📘 IT
11. Quick Summary Table

Concept Purpose Limitation

Objects Store data Field and record limits

Fields Store specific Field count limit

record data

Apps Group business Navigation bar limited

processes
 Relationships Link objects Lookup vs Master-Detail
rules

Formula Fields Auto-calculate data Read-only

Validation Enforce data quality Run only on save

Rules

Roll-Up Aggregate child Only Master-Detail

Summary data supported

ELEARNING IT
🏁 Final Conclusions
●​ Use Formula Fields for real-time calculations.​

●​ Use Validation Rules to maintain data accuracy.​

●​ Use Roll-Up Summary for automatic record aggregation.​

●​ Always design Relationships based on data ownership and dependency.​

●​ Combine Profiles, Permission Sets, and OWD for layered security.​