Salesforce Facts by Abhishek

Suppose we have an embedded screen flow in LWC and we are passing data from lightning record picker in LWC to the screen flow and we want that the change in record picker is reflected in screen flow instantly. We can achieve the same using bit of LWC logic. Reference:  https://salesforce.stackexchange.com/questions/408371/how-to-dynamically-change-flow-embedded-inside-lwc Attached are the screenshots.

Lightning record picker works with Custom Settings and Custom metadata as well. Attached are the screenshots.

We can create a dependent lightning record picker in LWC. Suppose, we have two record pickers and once the account record is selected, the second record picker should filter out the related contacts. Reference:  https://salesforce.stackexchange.com/questions/428066/lightning-record-picker-dynamic-record-filter-not-working Attached are the code snippets.

Here's another example of screen flow reactivity along with LWC lightning record picker. In this example, we have a picklist of list of user roles in screen flow and on selecting a role, we are showing a filtered record picker with users corresponding to the selected role. Attached are the screenshots.

We have a dynamic record picker in LWC. Using the combobox we can select the sobject and based on that we can set the objectApiName of the lightning record picker. Attached are the screenshots.

We have the new record picker component in LWC and that works perfectly as reactive in screen flow. Suppose, we have a datatable in screen flow which is displaying certain account records and once we select a row, we want to make use of the record picker to show only related contacts of the selected account for selection. In LWC, we make use of the getRecord() LDS function to set the filter value reactively based on each time the accountId is passed from screen flow to LWC. Attached are the screenshots.

So now we have lightning record picker base component in LWC. Using this we can create a dynamic record picker which can be used inside a screen flow and the parameters can be passed from the screen flow as per the requirement. In this example, we are fetching contact records which have both email and phone populated. Attached are the screenshots.