Salesforce Fact #824 | Simplifed check in validation rule

Suppose we have a use case in validation rule, where we need to restrict the change of some fields for all persona and if the user has a particular custom permission set assignment then the validation stays the same except for one field.

So, instead of repeating the condition check we can simplify the condition since few of the fields are anyways common:

OR(

ISCHANGED(AccountNumber),

ISCHANGED(AnnualRevenue),

IF(NOT $Permission.Test_Custom_Perm, ISCHANGED(NumberOfEmployees), FALSE)

)

In the above example, the user is restricted to update Account number, Annual Revenue and Numberofemployees fields with the exception for NumberOfEmployees if the user is assigned the Test_Custom_Perm custom permission.

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