Why Record Types Make Sense

Why Record Types Make Sense

Record Types aren’t just for making your org more complicated—they actually solve problems.

I had two teams using the same object in completely different ways. Instead of creating separate objects or overloading one layout, I created two record types with different picklist values and page layouts. It worked beautifully.

Field History Tracking Saved Me This Week

Field History Tracking Saved Me This Week

We had a weird situation where a record’s value had changed, but no one could explain why. That’s when I learned about Field History Tracking—and it totally saved my butt.

You can turn it on per object and select up to 20 fields to track. It’ll log changes in a related list, showing old value, new value, and who made the update.

Permission Sets: My Favorite Fix for Profile Headaches

Permission Sets: My Favorite Fix for Profile Headaches

I used to clone profiles to give different teams slightly different access… until I discovered Permission Sets. Now I’m obsessed.

Instead of creating a million profiles, I use one shared profile per job function, and layer access with permission sets.

Approval Processes Aren’t That Scary

Approval Processes Aren’t That Scary

I just built my first Approval Process and expected it to be way more complicated than it was.

One of our teams needed a way to flag certain requests for manager sign-off before they moved forward. Turns out, Salesforce has this built-in—and once I mapped it out, it actually made sense.

Scheduled Flows: Automating Reminders Without Apex

Scheduled Flows: Automating Reminders Without Apex

Today I created my first Scheduled Flows and holy crap—game changer.

We had a recurring need to remind consultants about pending service requests if they hadn’t updated them within 5 days. Instead of sending reminders manually, I built a flow that checks every morning and fires off emails automatically.

Process Builder: My First Real Automation Win

Process Builder: My First Real Automation Win

I just set up my first Process Builder flow that actually does something meaningful—and no one yelled at me for breaking anything!

The goal was simple: when a new case is created with a certain category, assign it to a specific queue automatically. Took a bit of trial and error, but it worked.

Validation Rules That Don’t Annoy Users (As Much)

Validation Rules That Don’t Annoy Users (As Much)

I’ve been adding more validation rules lately to keep our data clean, but I’ve also started getting feedback… and not all of it’s friendly.

Turns out, even a good rule can feel bad if it’s confusing or overly strict. So I’ve been tweaking my approach:

  • Write clear error messages that tell the user what to fix

  • Avoid blocking users unless it’s absolutely necessary

  • Use ISCHANGED() to stop users from accidentally triggering the rule when they didn’t even touch that field