Salesforce Fact #853 | Sobject update fact

In apex, if we add an sobject record to a list and then update any of the field value the final list would include that value. But that's not the case in case of flow.

In this example, we are adding an account record to a list and then updating the rating to 'Cold'. After DML is made on the list, the account rating would be 'Cold'.


In case of flow, it doesn't update the rating.

Note: As a best practice, always make the necessary updates to sobject record and finally add to the list. The above example is only for demonstration purpose and should not be followed.

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