Salesforce Fact #355 | Check converted account in record-triggered flow

Suppose we have a use case where we need to differentiate when an account record is created, whether it is an account created from lead conversion or not. The logic is to be checked in record-triggered flow on account.

Now, to achieve this we can create a field on account which would store the company of the lead getting converted. Also, on Lead we can create one formula field to store the company field value. The idea is, company is a required field on Lead and it would always have some value when the lead is getting converted. So, we can define a mapping from the Lead company formula field to the custom field created on account.

In the record-triggered flow, we can check whether the value of the custom field is populated or not to determine whether this is a converted account. 

Note: The custom field on account is only for the lead conversion purpose and need to be exposed in the UI, and also should not be updated from anywhere else.

In this example, we are updating the description of the account accordingly whether it is a converted account or not.

Attached are the screenshots.













Comments

  1. Ananda Deep MukherjeeMarch 21, 2022 at 8:18 AM

    Additionally or Optionally can we use the record.isConverted property for checking whether Lead is converted or not

    ReplyDelete
  2. Abhishek SahaMarch 22, 2022 at 2:58 AM

    Yes. you can.

    ReplyDelete

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more