Salesforce Fact #514 | Previous record type check in validation rule

Suppose we have a use case where we need to check previous record type name in order to put some validation when the record type is changed on the record.

Now, the limitation is PRIORVALUE() cannot take RecordType.Name or RecordType.DeveloperName as parameter. So, to resolve this we can create a formula field of text type which will hold the value of RecordType.DeveloperName and we can use this field along with PRIORVALUE() in our validation rule.

In this example, there are two record types: Test_RT1 and Test_RT2 in Account and we want to restrict the record type change from Test_RT1 to Test_RT2.

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