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.

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.

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.

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.

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.

Schema Builder has always looked a bit overwhelming—and honestly, at first I thought it was just for developers.

But this week I had to explain how several objects were related in a meeting, and the Schema Builder made me look like a total pro.

I thought I had everything set up perfectly… until a user messaged me saying they couldn’t see a field I definitely added to the layout. Turns out, I forgot to update the Field-Level Security (FLS).

Yeah. Oops.

Just because a field is on a layout doesn’t mean users can see it.

Today I learned why people complain about multi-select picklists—and I will probably avoid them forever now.

I created one thinking it would give users flexibility. But now I’m realizing:

• You can’t use multi-selects in many report filters

• They’re annoying to work with in Flows and formulas

• You have to use INCLUDES() instead of simple = logic