Salesforce Fact #832 | Screen flow: using Transform element result in datatable

In Screen flow, we can now use the Transform(Beta) element. We can use the result of the transform element in the standard screen flow datatable.

In this example, we have fetched few account records and showing those records in the datatable after doing some manipulation.

Couple of things to observe,

1) While trying to map in a sobject collection variable, the Id field is not available.

2) We have used BLANKVALUE() function on the account number, to show 'NOT AVAILABLE' when the account number is blank.

3) The TEXT() function is automatically added when mapping the picklist field values. It happened with the Industry and Rating fields.

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