Salesforce Fact #270 | Lookup filter in screen flow

Suppose we have a use case where we need to show only specific records in a lookup input field in screen flow. Now, the thing is the lookup field in the screen flow basically refer to an existing lookup field in the org, it is not a whole new field inside the flow. We need to specify the api name of the field as well as of the object.

Now, let's say we want to have a account lookup input in the screen flow which will show records only of a particular record for selection. For this, we need to create a lookup filter in that same field in the org.

In this example, we want to show account records which are having record type as 'Test RT1'. So we create a lookup filter on the Account lookup field on Contact.

Attached are the screenshots.





Comments

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