OrgReady

Salesforce Skills & Readiness

← Start Your Salesforce Career

Lesson 16 of 18 · 10–15 min

SOQL and DML Basics

A strong Apex foundation prevents small syntax lessons from turning into unsafe production patterns.

Learning sequence · data model first, security layers next
  1. What CRM and Salesforce Do
  2. The Salesforce Ecosystem and Major Clouds
  3. Org, App, Object, Field, and Record
  4. Standard and Custom Objects
  5. Common Standard Objects
  6. Field Types and Data Quality
  7. Objects, Fields & Records
  8. Lookup vs Master-Detail
  9. Many-to-Many Relationships and Junction Objects
  10. Profiles, Permission Sets & Object Access
  11. Field-Level Security
  12. OWD and Least-Privilege Record Access
  13. Opening Access: Role Hierarchy, Sharing Rules, Public Groups & Apex Sharing
  14. Apex First Steps
  15. Variables and Collections
  16. SOQL and DML Basics
  17. Why Asynchronous Apex Exists
  18. REST Callout Introduction

Your focus

Start Your Salesforce Career

FULL · Learn • Apply

  • Build and run the small example, then explain every line.

Learning objective

Explain and apply soql and dml basics in a small Salesforce scenario.

The concept

SOQL reads Salesforce records and relationships. DML inserts, updates, upserts, deletes, undeletes, or merges records. Query and DML limits make work outside loops a core correctness rule.

Worked example

Query open Opportunities once, update the collection in memory, and issue one update statement.

Read the requirement, identify the records and transaction, run the smallest example in a safe environment, inspect the result, and then add tests and bulk considerations before production use.

Query and update a collection

apex

List<Opportunity> deals = [
    SELECT Id, StageName
    FROM Opportunity
    WHERE CloseDate < TODAY AND IsClosed = false
];
for (Opportunity deal : deals) {
    deal.StageName = 'Closed Lost';
}
if (!deals.isEmpty()) update deals;

Common mistake

Copying a single-record example into automation without considering collections, limits, errors, or testability.

Interview angle

Explain the platform reason behind the syntax and state how the approach behaves for many records.

Pause and apply

What changes when this operation handles 200 records instead of one?

Official references

Reviewed 2026-09-23. Examples are illustrative; no code is executed here.

Key takeaways

  • Apex runs inside governed transactions.
  • Collections and bulk operations are the normal production shape.

Practice next

No linked assessment is available for this lesson. Use the pause-and-apply question to check your reasoning.

Reading these lessons does not yet save completion. Challenge results continue to provide assessment evidence.