Salesforce Fact #381 | Id comparison in validation rule

It is a good practice to not use hardcoded Ids anywhere in Salesforce. But in case we have some use case where we need to use hardcoded Ids in validation rule, then we need to be careful. 

If we are specifying the 18 char Id, then we need to use CASESAFEID function in order to make the comparison at the same level. However, it is not required if we are specifying 15 char Id.

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