Flow Screen Component: Dependent Picklists with RecordType and MultiSelect Picklist support

Howdy folks! 😀

In winter’19 release, the awesome flow product team released a flow screen component to support dependent picklist in flows. But sadly, this component didn’t support picklist value selection based on the record type. So, I came up with a Flow Screen Component: Dependent picklists based on RecordType selection. You’re welcome to check it out. 😀

But, there is always a but, guess what? That was still not enough.

Huh, why? That’s because we missed everybody’s favorite, the MultiSelect picklists(I hope, you got the joke. If not, contact Steve Molis!). So, basically neither of the components(Salesforce’s and mine) support a multiselect picklist as a dependent picklist.
So, it’s time we give an upgrade to this component.

In this article, I will be sharing the functional details of the component that I built to add the multiselect picklist support to the component, and how you can use it as an Admin or Dev.

So unlike in my previous post on dependent picklist component, I decided to keep it simple. So good news is I have bundled everything into an unmanaged package, which you can directly install into your Sandbox or Production. No fuss!

Link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t6F000001os5e

Note: I have tested the component quite well, but there is always a still. So you may run into some handled exceptions. In case you do, feel free to reach out, I will try to resolve the issue as soon as possible.

Lights, Camera and Demo!

Please note that the demo picklist values are also rendering based on the record type selection.

Thank you!


7 thoughts on “Flow Screen Component: Dependent Picklists with RecordType and MultiSelect Picklist support

  1. Pingback: Flow Screen Component: Dependent Picklists with RecordType and MultiSelect Picklist support by Narender Singh – UnofficialSF

  2. Hi Nerender,
    I just started using this component, which is GREAT and very needed. The one issue I am having is that if I pre-populate the RecordTypeId, I don’t get any values in the picklists. Is there a way to work around this?
    John Eichsteadt


  3. Narender, this is great! Do you have any guidance for how to use the “Selected Controlling Picklist Value” field? Ideally I would set a default value for it, but I’m having trouble getting it to work (I have tried typing in a text value and using a choice variable, but neither work). Thanks!


    • Hi Amy,
      The “Selected Controlling Picklist Value” is the that you will select in your controlling field picklist. So in order to get the selected value, you first create a text type variable, and then in the “Store Output values” section of component configuration, set the “Selected Controlling Picklist Value” field with the text variable.
      I am hope I am not sounding confusing. Let me know if that answers your question. 🙂


      • Thanks…. I don’t think I asked the question correctly, sorry! What I am looking for is to set a default input value for the controlling field picklist. Meaning, when the user gets to the screen with your component, the Controlling value is pre-populated based on their response to a question earlier in the flow. Then they simply select the Dependent values. Just curious if that’s possible. I hope I’m making sense! Let me know if I can clarify further.


      • Ahh, I see! Well, I intentionally made the component that way, where the user cannot pre-populate the controlling value. I wanted to keep it simple. Maybe in future I can give this an upgrade with some features.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.