R1D43 Getting Hands Dirty with Apex

| programming | salesforce |

I started my Salesforce Trailhead journey so that I could solve real problems that we have on my team. I took everything that I learned over the last few weeks and started working on one of those problems.

Like most things in life, everything looks very simple when you see it presented in a tutorial format, and then when you start to get in the weeds things become a bit more complicated.

The problem that I am trying to solve is to send some data to a third party service any time a deal closes. This requires thinking about a few things.

  1. Ensuring validation when the state of an opportunity changes to closed won.
  2. Firing off an event when that happens.
  3. Taking the data from the opportunity and formatting it properly as JOSN to send to the third party system.
  4. Find all the files attached to the opportunity (this turned out to be a rabbit hole of epic proportions.)
  5. Firing off the HTTP POST to the third party system. This includes figuring out some sane way to store the token safely.
Outside of #4 (so far) I have everything else more or less working. I learned a whole lot about Apex doing this hands on exercise.

Notably:

String descriptionTemplate = 
  'Account Name: {0}\n' + 
  'Account Email: {1}\n' +
  'Plan: {2}\n' +
  'Plan Description: {3}\n' +
  'Invoice Amount: {4}\n' +
  'Invoice Frequency: {5}\n';
I am looking forward to wrapping this up and moving on to the next, slightly more complicated problem that I am trying to solve with Salesforce.

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

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

`RunLore`: the SRE buddy that investigates incidents — and learns from every fix

What you learn during an incident usually disappears the moment it's closed. RunLore is an open source SRE agent that investigates, points you at the likely root cause fast, and turns every resolution into knowledge you can reuse.

via Ogenki July 12, 2026

“Not being good at something doesn’t mean you can’t love it.”

Perhaps ironically given the subject matter, I found this 34-minute video by Razbuten a bit intense, but I would still recommend it to people who work on onboarding, settings, etc.: In the video, the author tries to answer the question: how to make any giv...

via Unsung July 11, 2026

Generated and suppressed demand.

Eight years ago, I wrote about my theory of restoring struggling teams, which came down to four steps: A team is falling behind if each week their backlog is longer than the week before. Solve by hiring more. A team is treading water if they’re able to get...

via Irrational Exuberance July 11, 2026

Generated by openring