Salesforce Fact #382 | Lookup filter for particular profile

Suppose we have a use case where we need to restrict the records in the lookup for a particular profile. However, for rest of the users there should not be any restriction. Now, if we only include the condition for that particular profile then the search would get impacted for the other users as well. Therefore, we need to include the opposite filter as well.

In this example, we want that the users of the John & Team profile will get access to only those account records which are owned by them. However, there should not be any filter for other users. Hence, we have added the opposite filter as well and customized the filter.

Attached is the screenshot.



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