Category: Salesforce

It’s a little late to mention, but I’m attending DreamOle in Zaragoza, Spain tomorrow.

If you’re also attending, look out for me and I’ll be happy to meet you.

Here are the sessions in my agenda:

• Opening keynote
• Salesforce enhanced messaging and WhatsApp
• Customising record level security
• Demo battle
• Key architecture anti-patterns
• Closing keynote
• After party

They are offering an Agentforce Certification Bootcamp, in which you can obtain an Agentforce cert, but that hasn’t piqued my interest.… Read the rest

When creating custom fields, there are two settings most people ignore: External Id and Unique. When used properly, these boolean settings can be useful.

By setting a field as an External Id, you’re telling Salesforce that this field represents an Id field from a system outside of Salesforce.… Read the rest

There probably isn’t a single Salesforce project that has ever gone perfectly to plan.

Just like the sayings, “If you don’t make any mistakes, you’re probably don’t make anything”, and Mike Tyson’s popular one, “Everyone has a plan until you get punched in the face”.… Read the rest

Let’s say you have a record-triggered flow that calls a subflow. Sometimes you need to pass variables to the subflow.
If you need to pass a record to the subflow, you have two options:

1. Pass the just Id as a text variable
2. Pass the entire record

While both get the job done, I usually recommend option 1.… Read the rest

A LinkedIn article was published yesterday about hardcoding URLs in flows. The author is trying to solve a problem involving URLs that change depending on the environment.

For example, let’s say you have a screen flow that creates an account, and you want to display a link to the newly created account in the last step.… Read the rest

Every once in a while, when debugging flows, you may come across an error such as “Unable to obtain exclusive access to this record or 1 records: 003OL00000EMzT8YAL”

At face value, this error message doesn’t seem to tell you very much.… Read the rest

Record locking is when you inform Salesforce you want to lock a record for a certain period of time. Your process becomes the only one that can access that record. Any other processes that attempt to access it at the same time receive an error.… Read the rest

How that we’ve covered flow bulkification and flow interviews, we can tie things together. As mentioned, sometimes Salesforce automagically bulkifies flow interviews.

Most of the time, this is a good thing. Sometimes it’s not so good.

For example, imagine a flow that gets and updates a custom setting.… Read the rest

In Salesforce, there are two flow parts: the building part and the execution part. Here are some interesting things to know about the latter.

Each time a flow executes, Salesforce creates an instance of the flow. The instance is a standalone unique copy of the flow, running within a specific context.… Read the rest

Most good Salesforce consultants are already familiar with good flow practices. Things like

• Don’t create/update/delete records (DML operations) within loops
• Don’t do multiple gets of the same record or related records
• Don’t update the triggering record in an after-save flow
• Etc.

Every once in a while, it’s interesting to see how our parent company is doing. You know, the big one that we all depend on for our livelihood.

This income chart was recently released:

It’s interesting to notice a few things:

1. Service income is greater than Sales.

A couple of readers provided some feedback from yesterday’s email that I felt added to the conversation.

The 1st is the option to use validation rules for required fields. This approach has pros and cons.

Pros:

• Fields can be conditionally required by value.

When creating required fields on a standard or custom object, you have two options:

1. Make them required at the object-level
2. Make them required at the UI-level

In most cases, the latter is a better option. Why?

When fields are required at an object level, they are *always* required, regardless of the source.… Read the rest

Last week I wrote about how, despite the trending chatter, I don’t believe AI will fully replace developers in the short term.

Today I had a conversation with a colleague about this topic, and another interesting consideration arose.

If AI writes the apex code, who’s ultimately responsible for it?… Read the rest

In addition to the spanning relationship limit, there are some other important considerations when using formula fields. There are 3 more:

1. Character limit
Formula fields can have a maximum of 3,900 characters. This includes spaces, carriage returns, and comments.

You can easily solve this limit by reducing spaces, or by splitting the formula into sub-formulas.… Read the rest

When attempting to update a client’s formula field on an object, I received an uncommon error message. Salesforce complained, “You have reached the maximum number of object references”.

This error is caused by trying to exceed the limit of cross-object references (also known as “spanning relationships”).… Read the rest

When building flows, it’s common to have input and output variables. Whether passing the current record Id to a screen flow or calling an autolaunched subflow, these variables keep things modular.

Here’s a small tip I haven’t seen often: When using an input variable, only use it once.… Read the rest

There’s more and more chatter about AI replacing developers. Mark Zuckerberg talks about it often these days, and even Marc Benioff has made more than a few comments about it.

While it’s hard to predict the near future, I’m pretty sure about the state of AI today.… Read the rest

There are multiple ways to debug flows in Salesforce.

The debug button
The first option is the most popular. You create the flow and then click “Debug” to see it run. By the way, if your flow has input variables, there’s a way to speed up the debugging process.… Read the rest

I bet you think this email will be about Salesforce flows, eh? Well, it’s not. Instead it’s about flow state.

According to Wikipedia, “Flow state theory suggests that when individuals are in a state of flow, they experience deep immersion, focus, and intrinsic motivation in their activities.”… Read the rest

A Salesforce client of yours has a problem, so they reached out to you for help.

They’ve explained the issue, you’ve repeated it back to them to confirm your understanding, and now it’s time to make a decision. Also let’s remove urgency from this scenario, as that would clearly encourage you in one direction.… Read the rest

The repeater component is a relatively new feature in screen flows.

A simple way to show its usefulness is through an example. Let’s imagine there’s a Payment object, which is related to the Opportunity. Rather than have your users click “Add” on the Payment related list, enter some data, and then click “Save & New”, you can offer an optimized screen flow with a repeater.… Read the rest

Here are three other mechanisms to avoid race conditions in flows.

1. Add a wait element
Place a wait element after an update, create or delete element. The wait time can be as short as 1 minute, but this ends the current transaction and commits (saves) the operations to the database.… Read the rest

There are a few articles about how to create platform events in Salesforce, but most of them have lots of fluff and unnecessary details. So here’s a concise version.

We’ll use the Nonprofit Success Pack (NPSP) example, in which a household account is created when a contact is created.… Read the rest

In response to Friday’s email regarding race conditions, a fellow reader suggested using platform events.

This is another great option, if you know how to use them.

If you don’t, here’s a quick synopsis:

When things happen in Salesforce, you may or may not be aware of it.… Read the rest

A race condition is when multiple transactions are happening at more or less the same time, and they conflict.

Let’s say both transaction A and B look to see if a record exists. If it doesn’t, they create it. Now if A and B happen virtually simultaneously, they both create records and therefore cause duplicates.… Read the rest

In a flow, it’s usually a good idea to keep the labels of elements short and sweet. For example, you don’t need to specify which field(s) you’re actually updating in an update element.

I’ve seen consultants use “Update Billing Address on Account” for such an element.… Read the rest

It is with great pleasure to announce that I’ll be attending the True North Dreamin’ (TND) conference this year.

TND was absent during the pandemic, so this is first reappearance in many years. There aren’t a ton of community-led Salesforce conferences in Canada, so each one counts.… Read the rest

There’s an important distinction between navigating and searching.

Navigating a site is usually a user’s first action. They visit your Experience Cloud, scan the content and perhaps click on a few menus. They usually have a reason to come to the site, and are looking for something in particular.… Read the rest