LESSON 1.5 · ABOUT 20 MINUTES
Developer & integration foundations
Understand when to use queries, code, and APIs in a support workflow.
By the end of this lesson
- Read a simple SOQL query.
- Explain bulk processing and duplicate-safe integrations.
Query intentionally
SOQL retrieves Salesforce records and selected fields. Example: SELECT Id, Subject, Status FROM Case WHERE IsClosed = false LIMIT 20. Choose only necessary fields and respect the access requirements of the execution context.
Think in collections
Salesforce code runs within transaction limits. Avoid SOQL or DML inside a loop over records; collect identifiers, query related data once where practical, and perform bulk operations. Tests should include multiple records and failures.
Design for retries
An integration can receive the same event twice. A stable external identifier and an upsert strategy can prevent duplicate records. Authentication, permissions, error responses, retry policy, and auditability are part of the integration design.
Worked example
An external system retries creation of the same Case after a timeout. How can you avoid duplicates?
Store a stable external ticket identifier in an appropriately configured external ID field and design an upsert flow around it. Confirm uniqueness and handle conflicts; do not use the subject text as the identity.
Continue with the official resource: Salesforce developer documentation