LinkedIn

Usage of new ISCLONE() function in Record Triggered flows and Considerations

-


Overview

ISCLONE() is available in flows as part of Winter 23. So let us see a use case where we can use ISCLONE in flow and what are some considerations compared to the same implementation using Apex.

Use Case

The account is having 2 record types:

1. Standard

2. Premier

Both are assigned to different page layouts


In standard Account Layout, we have a new custom look-up added called Primary Contact, but it is not added to Premier Account Layout.


Since Clone is not available by default in Account - we need to create a custom clone button and add it to Premier Account Page layout:


Problem Statement

1. Create a new Standard Account by populating Primary Contact

2. Convert it to Premier Record Type

3. Clone the Account and create a new Account

4. Check the Premier Contact value in the new Account - Value is empty

Reason

Standard clone can only clone field values present in the UI. Since primary contact is not added to Premier Account it is not copied over to the new account.

How to Solve - Trigger

Since flow was not supporting an option to check if the new record is a cloned one, the traditional option is to use a trigger solution like shown below:

1. Check if the current record is a clone if so get the source id

2. Query the source Account to get primary contact and copy it over to the new Account


Since we have ISCLONE() available in Winter 23 - let us see how we can use this to solve the above problem:

How to Solve - Flow

We can create a record-triggered flow to solve this:

Step 1 - select an object and the trigger option


Step 2 - Add entry criteria


You can see ISCLONE() function is added as a criteria

Step 3 - Get Source ID

Unfortunately, flow is not supporting a mechanism to get the source id of the cloned record. So we need to use an apex action to get this value.

and call this from Flow:


Step 4 - Retrieve Primary contact


Step 5 - Update New Account with primary contact


The final Flow looks like below:


Considerations

1. Since we do not have a mechanism to fetch source id in flow we need to use apex to do that

2. Since apex actions are not supported in before flows - we need to use after insert flows to implement this

3. Since this is after flow - we need to execute an additional DML to update the primary contact. But in trigger, since this is before flow we can save one DML

Demo



Comments

Post a Comment

Popular posts from this blog

Subscribing to Salesforce Platform Events using External Java Client - CometD

-
Image
Platform Events follow event based Architecture, where multiple subscribers can subscribe to a published event in real time manner.  Below diagram shows the basic Architecture of the event-based communication Model: Event - This is a change in state for a business process Event Message - Data about the event Producer - Publisher of the event Event Bus - A communication and storage service for published events Event Consumer - A subscriber to the channel Platform events can be subscribed internally and also externally Platfrom events  - Internal Subscription Below are some scenarios in which you can consume platform events internally: 1. When we need to execute functionalities asynchronously to save govornor limits 2. To build a proper exception logging framework - You can find more details here  How to subscribe Internally? we can see more details about this in a different blogpost. Platfrom events  - External Consumption Many Organizations are moving to event-based integration appr
Read more

Salesforce Security - Restriction Rules and Scoping Rules

-
Image
1. Overview Salesforce provides a very effective security model where we always start with the most restrictive access and then open up access using additional mechanisms like sharing rules, and manual sharing based on the requirements.   But there might be scenarios where we need to restrict access based on specific criteria. Salesforce recently introduced 2 approaches to support this requirement. Those are restriction rules and scoping rules. Let us see this in detail. 2. Restriction Rules - Overview Using restriction rules we can apply an additional level of filter on top of records to which a specific user is having access. 3. Scoping Rules - Overview Scoping rules help to filter the default records visible for a user based on specific criteria. But it is not preventing access to other records. 4. Compare Restriction Rules and Scoping Rules 5. Restriction Rule - Example Company ABC is having Job Applications getting created through their company portal and synched to Salesforce. T
Read more

How to develop reusable Invocable Apex methods for Flows

-
Image
 Salesforce is adding many new features and capabilities to Flows. But there are still some scenarios where you need to call apex methods from Flows to execute complex operations - when Flow is not capable of doing that or the performance will be low when you implement that using flows. Let us see how we can build reusable apex methods for Flows. For this let us consider 2 sample scenarios: Scenario 1 - Quick Create Account/Contact I want to build a screen, where the user can select the object needs to be created, and then create a record of that object by entering the required details. Also if the record creation is getting failed, I want to create an exception record with details. Solution Let us see how we can utilize Apex action for this. For this first let us create an Apex Invocable method, which can accept a list of wrapper class as shown below: You can see, this invocable method is accepting a List of wrapper class variables and also returning a list of wrapper class variables.
Read more