Apex Triggers
I worked on the Apex Triggers module on trailhead. Apex triggers are very similar to database triggers (remember those?). I remember in my first job, which was an enterprise healthcare company, our DB was littered with hundreds of triggers that did various actions whenever records were inserted, updated, or removed.
Triggers are a powerful concept, but tend to be very difficult to maintain at a large scale. Especially when you have a large team. I think they are an artifact of the legacy development methodologies. These days most of the actions that triggers used to be responsible for are managed as either a part of the model, or as separate background tasks.
Despite this being true in most modern software development, Salesforce allows you to write triggers in a first class way that do things when records change. I think this is a case where they are still “ok” to use because they remove a lot of the overhead with having to figure out how to keep track of the state of all of your various records.
The best part about Apex triggers is that unlike DB triggers which require you to write your code in an enhanced variant of SQL, Apex triggers allow you to write the code in Apex. This means that you can take full advantage of all of the built in salesforce libraries, as well as making HTTP callouts (the most powerful part of all of this) in a really simple way.
One thing to note is that if you do make HTTP callouts with Apex, you must do so asynchronously.
Apex triggers have a handy access to the context that fired the trigger, including both the old and new state of the affected object.
One great hint that the module gives us is to write our code to support both single and bulk operations. While most triggers that I have written operate on only a single object at a time; there may come a day when I may want to do work on multiple objects at a time. For example, if I was using the bulk API. By writing the code in a way that supports bulk operations (essentially using a for loop) you can reuse the same code in the future rather than having to handle both cases separately.
Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.
Check out some more stuff to read down below.
Most popular posts this month
- 2024
- Reinstalling Windows at 1am
- SQLite DB Migrations with PRAGMA user_version
- My Custom Miniflux CSS Theme
- How to Disable Wayland in Debian Testing
Recent Favorite Blog Posts
This is a collection of the last 8 posts that I bookmarked.
- The AGI economy is coming faster than you think from Freethink
- Rolling the ladder up behind us from Xe Iaso's blog
- In Praise of “Normal” Engineers from charity.wtf
- Reports of Bluesky's death have been greatly exaggerated from The Torment Nexus
- What Would a Kubernetes 2.0 Look Like from matduggan.com
- We Can Just Measure Things from Armin Ronacher's Thoughts and Writings
- workflows for ai coding from /* 🤖🛠️ */
- Reinvent the Wheel from Matthias Endler
Articles from blogs I follow around the net
in the heat of the summer better call out a plumber
Back in the old days, the good old days, when it was generally accepted that Fascism and Nazis were bad, bloggers would write these posts that were sort of recaps […]
via WIL WHEATON dot NET June 20, 2025Just one more Patreon indignity
I was today years old when I learned that Patreon offers no mechanism to download all of your own posts from your "creator" account. Because fuck you that's why. Confirmed with "support" [sic] who sent me a response with the level of ov…
via jwz June 20, 2025Pluralistic: Oregon bans the corporate practice of medicine (20 Jun 2025)
Today's links Oregon bans the corporate practice of medicine: Karma for Unitedhealthcare, Part II. Hey look at this: Delights to delectate. Object permanence: 2015, 2020 Upcoming appearances: Where to find me. Recent appearances: Where I've been. …
via Pluralistic: Daily links from Cory Doctorow June 20, 2025Generated by openring