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.
Standalone posts that live outside the blog, courses and training.
Twenty minutes from a blank class to a tested, mocked, named-credential callout — narrated, mistakes left in.
Two systems talking directly is simple right up until it is three systems, then five. Where the line actually sits.
Nightly loads still run the world. Upsert on external IDs, order parents before children, and make reruns safe.
When the caller does not need an answer, publish an event and move on — decoupling, replay, and the delivery guarantees you actually get.
The synchronous callout, done properly: named credentials for auth, a timeout you chose on purpose, and a mock for the test.
Business Basics
Your after-update updates the record, which fires your after-update. Breaking the loop without breaking legitimate re-entry.
Business Basics
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'.
Business Basics
One method per event, a static bypass flag, and constructor-free classes your tests will thank you for.
Business Basics
Two triggers on one object run in an order Salesforce refuses to promise. The fix is a rule, not a framework.
Many-to-many done properly: two master-details, sharing inherited from both sides, and a real example built end to end.
The one Setup tool that shows your data model as it is, not as the ERD on the wiki claims it is.