Last Updated on August 3, 2023 by Rakesh Gupta

Big Idea or Enduring Question:

• How do you write a validation rule using before-save record-triggered flow without creating extra metadata?

Objectives:

After reading this blog, you’ll be able to:

• Understand validation rule
• User record-triggered before-save flow to create a validation rule
• Show the error message at the Top of the Page
• And much more

👉 Previously, I’ve penned several posts on the validation and Salesforce Flow. Why not check them out while you are at it?!

1. Adding Validation to Flow Screen Components
2. Validation Rule using a before-save Flow? Yes!
3. How to Fix FIELD_CUSTOM_VALIDATION_EXCEPTION Error)

Business Use case

Benjamin Moore, a Salesforce Administrator at Gurukul On Cloud (GoC), has been tasked with a specific requirement. He must restrict users from creating a new opportunity within the account if an open opportunity exists. The following text should be utilized for the error message:

Please utilize the existing open opportunity within this account. If you need further assistance or have questions about managing opportunities, please contact IT support.

What is Before Save Flow?

The Before-save Flow is a trigger that is performed before an operation – such as an insert, update, delete, etc. You can use such a Flow to check or change values ​​before data is updated or inserted in the database. A Before-save is much faster because each record is not saved to the database again. Avoiding that extra save procedure means skipping another round of Assignment rules, Auto-response rules, Workflow rules, and other customizations that take time to execute. Use a Before-save Flow on the following use cases:

1. Update fields on new or changed records – means that you want to update the fields on record that started the Flow
2. Trigger a Validation rule (Not needed after the winter’24 release)

Read this article to learn more about when to use before-flow vs after-save flow.

Automation Champion Approach (I-do):

After Winter ’24 release, you can now create a complex validation rule that was previously unachievable using a standard validation rule. This can be accomplished through the use of before-save flow, combined with the newly introduced custom error component.

Before discussing the solution, let me show you a diagram of the process at a high level. Please spend a few minutes going through the following Flow diagram to understand it. Let’s begin building this automation process.

Guided Practice (We-do):

There are 5 steps to solve Benjamin’s business requirement using Record-Triggered Before-Save Flow and the newly introduced Custom Error element. We must:

 

1. Define flow properties for record-triggered flow
2. Add a decision element to check if the record was created or updated
3. Add a get records element to find related open opportunities
4. Add a decision element to check if the open opportunities were found or not 
5. Add a Custom Error element to show custom error messages.

Step 1: Define Flow Properties

1. Click Setup.
2. In the Quick Find box, type Flows.
3. Select Flows, then click on the New Flow.
4. Select the Record-Triggered Flow option, click on Create
   1. Object: Opportunity
   2. Trigger the Flow When: A record is created or updated
   3. Set Entry Conditions: None
   4. Optimize the Flow For: Fast Field Updates
5. Click the X at the top to save your changes.

Step 2: Using Decision Element to Check if the Opportunity Was Created or Updated

Now we will use the Decision element to check if the opportunity record was created or updated. 

Step 3: Adding a Get Record Element to Find Related Open Opportunities

The next step is to use the Get Records element to find related open opportunities on the account.

1. On Flow Designer, below the Created node, click on the +icon and select the Get Records element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Select the Opportunity object from the dropdown list.
4. Select All Conditions Are Met (AND). 
5. Set Filter Conditions
   
   1. Row 1:
      1. Field: AccountId
      2. Operator: Equals
      3. Value: {!$Record.AccountId}
   2. Click Add Condition
      1. Row 1:
         1. Field: IsClosed
         2. Operator: Equals
         3. Value: {!$GlobalConstant.False}
6. How Many Records to Store:
   1. select All records
      
7. How to Store Record Data:
   1. Choose the option to Automatically store all fields. 
8. Click the X at the top to save your changes.

Step 4: Using Decision Element to Check If Open Opportunity was Found or Not 

Now, we will use the Decision element to check if the previous Get Records element returns open opportunities record. 

1. On Flow Designer, click on the +icon and select the Decision element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Under Outcome Details, enter the Label the API Name will auto-populate.
4. Condition Requirements to Execute Outcome: All Conditions Are Met (AND)
   1. Row 1:
      1. Resource: {!Get_Related_Opportunity}
      2. Operator: Is Null 
      3. Value: {!$GlobalConstant.False}
5. When to Execute Outcome: If the condition requirements are met.
6. Click Done.

Step 5: Adding a Custom Error Element to Show Error Messages

1. Under the Yes node, select Custom Error element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Set Error Message 1 Details
   1. Where to Show the Error Message: In a window on a record page
   2. Error Message:
      
      1. Please utilize the existing open opportunity within this account. If you need further assistance or have questions about managing opportunities, please contact IT support.
4. Click the X at the top to save your changes.

In the end, Benjamin’s Flow will look like the following screenshot:

Once everything looks good, perform the steps below: 

1. Click Save.
2. Enter Flow Label the API Name will auto-populate.
3. Click Show Advanced.
4. API Version for Running the Flow: 59
5. Interview Label: Custom validation Rule Using Flow {!$Flow.CurrentDateTime}
6. Click Save.

Almost there! Once everything looks good, click the Activate button.

👉 Check out the video for step-by-step instructions.

Things to Remember

1. The limit for the error message field is 255 characters.
2. You’re only allowed to add one error message for a page.
3. You’re only allowed to add one error message per field.
4. it is not possible to use the link with your error message.
   1. escape parameter Indicates whether any HTML markup in the custom error message should be escaped (true) or not (false). This parameter is ignored in both Lightning Experience and the Salesforce mobile app, and the HTML is always escaped. The escape parameter only applies in Salesforce Classic. Read this article for more information.

Proof of Concept

From now on, if a user attempts to create a new opportunity on an account that already has an open opportunity, the record-triggered flow befoe-save we’ve created will be triggered and display an error message.

 

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.