Walk the training path

Module 5 sections

Business Basics

The reader knows nothing about business, software or careers. Salesforce is not mentioned until S16. Every term used later in the curriculum is born here, in the order a human brain needs it

Start

1. 01 · Order of execution, the map Before triggers, validation, after triggers, assignment rules, flows, roll-ups — what actually runs when you press Save. 15m
2. 02 · One trigger per object Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework. 10m
3. 03 · The handler pattern One method per event, a static bypass flag, and constructor-free classes your tests will thank you for. 15m
4. 04 · Bulkification: 200 records or bust Triggers receive up to 200 records at once. Every query and DML statement inside a loop is a countdown to 'Too many SOQL queries: 101'. 15m
5. 05 · Recursion control Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry. 10m

Module 5 sections

Data Model Basics

Objects, fields and relationships — how Salesforce actually stores your data, and how to shape it.

Start

1. 01 · Standard objects vs custom objects Account, Contact, Opportunity, Case solve more than you think — the checklist to run before you create anything custom. 10m
2. 02 · Relationship types, decided with three questions Lookup, master-detail or junction — answered by ownership, cascade delete, and roll-ups. 15m
3. 03 · Record types and when not to use them Record types shine for genuinely different processes on one object — and multiply your maintenance everywhere else. 10m
4. 04 · Schema Builder, the honest map The one Setup tool that shows your data model as it is, not as the ERD on the wiki claims it is. 10m
5. 05 · Junction objects in practice Many-to-many done properly: two master-details, sharing inherited from both sides, and a real example built end to end. 15m

Module 5 sections

Integration Patterns

REST, platform events and middleware — moving data without losing it.

Start

1. 01 · Request-reply with named credentials The synchronous callout, done properly: named credentials for auth, a timeout you chose on purpose, and a mock for the test. 15m
2. 02 · Fire-and-forget with platform events When the caller does not need an answer, publish an event and move on — decoupling, replay, and the delivery guarantees you actually get. 15m
3. 03 · Batch sync without tears Nightly loads still run the world. Upsert on external IDs, order parents before children, and make reruns safe. 15m
4. 04 · Middleware or point-to-point? Two systems talking directly is simple right up until it is three systems, then five. Where the line actually sits. 10m
5. 05 · Watch: a callout built end to end Twenty minutes from a blank class to a tested, mocked, named-credential callout — narrated, mistakes left in. 20m