Salesforce Fact #442 | Another awesome feature of record-triggered flow

Most of the time we execute some custom logic when there is any change in the value of specific fields of the record. But what if we need to detect if there is any change in the record i.e. there is a change in any of field (excluding audit fields and formula fields obviously!).

Salesforce record-triggered flow has this awesome feature where we can compare the previous and current state of the record, without specifying any field explicitly.

In this example, we have set up a record-triggered flow on Account and it checks if there is any change in any of the field value and if it is, then it updates the description with some text.

Attached are the screenshots.



Now, once the record is created, updating no field.


Now, updating Account Source.




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