Salesforce Fact #729 | LWC getRecords in screen flow

Suppose we have a lookup component in the screen flow which allows selecting multiple accounts. Now, we have a requirement to get the data of the selected accounts.

We can get that using an LWC which makes use of getRecords wire method to fetch the required data and display in the UI.

References: https://developer.salesforce.com/docs/platform/lwc/guide/reference-wire-adapters-records.html

https://dev.to/tdrnk/lwc-getrecords-wire-adapter-how-to-retrieve-records-dynamically-apd

Note: The LWC UI styling can further be improved. It is just for demonstration purpose.

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