Quick Choice – Improved Picklists and Radio Buttons for Flow

This Post was most recently updated on: 09/14/20

Quick Choice is a flow screen component that provides some features that aren’t available in the current picklist and radio button implementation in Flow Builder.

Features that it provides:

  1. Accepts as an input a pair of string collections.
  2. Can accept a default value that’s dynamically determined by your Flow
  3. Can generate picklists from existing picklist fields with optional filtering based on record type
  4. Supports ‘None’ Value and Requiredness
  5. Choices can be formatted as Radio Buttons, Picklist, or Visual Cards
  6. Visual Cards can be displayed with or without Icons or Images
  7. Visual Cards can be displayed in single or dual columns
  8. Specify the width of the picklist.

Note: the rest of this post focuses on the Quick Choice component. If you are interested in learning more about the initial example shown in the above video, where different record forms are displayed based on Record Type, take a look at the posts about Record Detail, Get Layout Fields and Get Layout By Record Type and Profile, and Get Record Type by Object

Quick Choice supports both picklists and radio button groups, set by passing in a value for Display Mode. For this document, we’ll always use “Picklist”. There’s no support for multiple select. If you need that, consider the Dual List Box flow screen component.

Creating Choices from String Collections

Use String Collections as your inputs by setting Input Mode to “Dual String Collections”. Pass in one collection for Labels and one for the underlying values (A typical use case for this is when you want your user to see a list of friendly labels, but you need to make sure that you can get the recordId of the selected label.)

Example: You want your flow to let the user choose a record type from a picklist and then display the layout corresponding to that record type (This is demonstrated in the video above). The Quick Choice package includes several utility actions that make this easy. You first start out with the GetRecordTypeInfobyObject action, which returns separate collections of recordTypeNames and Ids. You then use those as inputs to a QuickChoice control. When the user makes their choice, you use a couple of additional utility actions to extract the Layout fields for the layout that corresponds to the combination of the selected RecordType and the running user’s profile. The layout fields are then passed to the new RecordDetail flow screen component.

Tip: If you are starting with a collection of SObjects instead of a collection of Strings, you can use the ExtractFieldFromCollection flow action (provided in the same package as SmartChoice) but you’ll need to modify its Apex, swapping the references to “Account” for your chosen SObject.

Creating Filtered Choices from Picklist Fields

Many orgs take advantage of the ability to create record-type-specific sets of picklist values for picklist fields like Account.Type and Account.Rating. Flow already enables the easy creation of Picklist Choice Sets, which point at an existing picklist field. But you can’t filter a Picklist Choice Set on a specific Record Type. Quick Choice allows you to do that.

Start by setting the Input Mode to “Picklist Field”.

Pass in strings for Object Name and Field Name. (You can also use Object and Field picker)

Pass a record type ID in. If you don’t, the component uses the ID of the standard “Master” record type ID, which will result in no filtering. This package includes a useful utility function called GetRecordTypeInfoByObject that will return the record type Id’s and Labels for a given object type name. The video above shows how you can use QuickChoice first to let the user select a record type and then to show a set of filtered picklist fields. Learn more about using a Flow Action to retrieve the available record types so your user can pick the one they want.

Displaying Choices as Visual Cards

Set the Display Mode to “Card” and the Input Mode to “Visual Text Box” .

Pass in a collection of Strings in Choice Labels for the visual card headers, a collection of Strings in Choice Values for visual card descriptions and optionally a collection of icon and/or image references in Card Mode – Choice Icons for visual card icons.

If you are displaying icons, set the Card Mode – Include Icons in Display Box? parameter to True and set the Card Mode – Icon Size parameter.

The visual cards are displayed in a single column by default. Set the Card Mode – Number of Display Box Columns (1 or 2) parameter to 2 to display dual columns.

Visual Cards without Icons

Visual Cards with Icons

Dual Column Visual Cards

Requiredness Support

You can set the Required field to $GlobalConstant.True. If you do, Flow will prevent screen transition if the user selects ‘None’ or makes no selection at all.

Controlling the ‘None’ Choice

By default, there will be no “None” Choice. To add one, set the input “Allow None To Be Chosen” to $GlobalConstant.True.

Multiselect Picklists

Not supported directly with this component, but check out Dual List Box.


General Attributes

Master LabelStringThe main label for the picklist or radio button group
Display ModeEnumEither “Visual”, “Picklist” or “Radio”, depending on which control you want
Input ModeEnum“Single String Collection”, “Dual String Collections”, “Picklist Field”, or ” Visual Text Box ” are currently supported
RequiredBooleanWill prevent transition if set to {!$GlobalConstant.True}
ValueStringThe selected value. This can be passed into QuickChoice, allowing you to set the default value dynamically.
Allow None To Be ChosenBooleanSet this to true to include a None choice. (For Input Mode “Picklist Field” only)
Set Width in PixelsIntegerSet the width of the component for Picklist & Radio Buttons (Default 320 pixels)
allValuesString[]The complete set of values provided to the user. (V1.3+)
allLabelsString[]The complete set of labels provided to the user (V1.3+)
selectedLabelStringThe selected Label (V1.3+)

Additional Attributes When Using Input Mode = “Single String Collection”

Choice ValuesString CollectionThe values of your choices (The same collection will be used for Labels and Values)
The selected Label/Value will be returned by the component

Additional Attributes When Using Input Mode = “Dual String Collections”

Choice LabelsString CollectionThe labels of your choices
Choice ValuesString CollectionThe values of your choices (should be unique)
The selected Value will be returned by the component

Additional Attributes When Using Input Mode = “Visual Text Box ”

Choice LabelsString CollectionThe labels of your choices (should be unique)
The selected Label will be returned by the component
Choice ValuesString CollectionThe values of your choices (This is provided as extra descriptive text in the visual card)
Card Mode – Choice Icons
String CollectionMix and Match either:
– Icon names formatted as icon_type:icon_name (Example “utility:attach”)
See complete selection at https://lightningdesignsystem.com/icons/
– Image names formatted as filename.ext (Example “astro.png”)
Referenced images must be included in a ZIP file referenced by a Static Resource* named Quickchoice_Images. Note that this Static Resource is created by the package and you can edit it and upload a new zip file.
Card Mode – Include Icons in Text Box?BooleanDisplay the provided icons in the visual card
Card Mode – Icon SizeStringOptions include x-small, small, medium, or large. This value defaults to medium.
Card Mode – Number of Textbox Columns (1 or 2) String1 or blank (default) for a single column or 2 for dual columns

Additional Attributes When Using Input Mode = “Picklist Field”

Object Name (for Picklist Field)StringExample: “Account” (this component no longer uses the combined “Account.Type” as an input)
Field Name (for Picklist Field)StringExample: “Type” (this component no longer uses the combined “Account.Type” as an input)
Record Type IdStringThis will default to the id of the Master record type

*NOTE: Static Resource
The package includes a Static Resource named Quickchoice_Images. To access your own images, create a ZIP file containing all of the images you want to reference and then, in Setup, Edit the Quickchoice_Images Static Resource and reference your ZIP file with the “Choose File” option. To learn more about Static Resources and creating ZIP files, see the Instructions for my ersQuickSwitchApp component.


Before installing this component you need to have on your org the Flow Base Components support package, version 1.2 or greater.

Install that here.

Current Version

Version 2.31 Unlocked – 9/14/20 – Eric Smith

Release Notes:

Version 2.3 – Eric Smith – 9/14/20
Fixed Visual Card selection bug when no Master Label is provided

Version 2.2 – Eric Smith – 9/2/20
Includes a new option to sort the values in the Picklist

Version 2.1 – Now includes a CPE (Custom Property Editor)

View Source


Old Versions (not recommended)

Version 2.2 Unlocked – 9/2/20 – Eric Smith

version 2.1 Unlocked

Version 2.0 Unlocked 

Version 1.4 Managed 6/5/20

Version 1.4 – 4/19/20 – Eric Smith

Version 1.3

3/2/20 Eric Smith
v1.27 Added ability to display both images & icons on visual cards (Thanks again to clifford-fra for the update)

Unmanaged v1.27 (Production/Developer)
Unmanaged v1.27 (Sandbox)

2/6/20 – v1.26 Display a Visual Card as preselected when passing in a default value (Thanks to clifford-fra for the fix)

Unmanaged v1.26 (Production/Developer)
Unmanaged v1.26 (Sandbox)

Unmanaged V1.24

See Release Notes

1/16/20Eric Smith
v1.23 – Added an option to display the visual cards in a single or dual columns

Managed V1.23 (Production/Developer)
Managed V1.23 (Sandbox)

1/3/20 -alexed
v1.20 – changed actions to global from public to make them visible in flow builder.

12/31/19Eric Smith Enhancements
v1.17: Added visual text box selection with or without icons. Fixed error handling when Required is set to True

v1.13: Fixed bug with defaults on picklist control. Added flag to allow or disallow a ‘None’ choice

Notify of
Inline Feedbacks
View all comments
Ed Santandrea

5/14/20 – It seems I am getting an error when installing directly into my sandbox (using the Sandbox link).

I tried installing for Admin as well as All Users. Also tried changing “What if existing component names confflic….” set to Do Not Install as well as Rename conflicting…

“This app can’t be installed.
There are problems that prevent this package from being installed.
Invalid reference
c..NotSupportedMessage recordDetailFSC: Invalid referencec.NotSupportedMessage of type label in file
of type label in file recordDetailFSC.js

Scott Fenech

I’m getting the same error.

Alex Edelstein

I think this error has been fixed in the current version. Are you trying to install version 1.4?


I get the same error. Installing the latest version in a sandbox.


I am also getting the same error with the latest version in a Sandbox.


Before Installing the package, try manually adding this custom label in the target org:

Short Description: NotSupportedMessage
Name: NotSupportedMessage
Categories: messages
Value: Unable to access a field called

Alex Edelstein

You can also address this by installing version 2.0, which is now the recommended version. Available above

Cris Zuniga

Hello, I am also getting an error when downloading v1.27 to a sandbox. I checked the “Rename conflicting…” and am getting this error: “The name “MockHttpResponseGenerator” is already used on component type: Apex Class. Please rename existing component.”

Alex Edelstein

That problem has been fixed in more recent versions, Cris. Is there a reason you’re installing an old version?


Hi, sorry for such stupid questions – but… I did previously install the unmanaged package (1.27 Sandbox). Then played around developing some flows. Now I’m coming across an issue: one screen, three QC components for three fields (custom object) only one component is displayed shuffling the order hides all three whereas another screen with three QC components has no issues (Account object) So I thought I’d “upgrade” first… Now – how do I “upgrade”? If I want to install I get: This app can’t be installed. There are problems that prevent this package from being installed. Duplicate NameThe name “quickChoiceFSC”… Read more »

Alex Edelstein

Salesforce generally prevents you from overwriting existing stuff. Because the new versions have changed enough to be considered different, you need to either delete your existing version before installing the new version or wait for us to create a managed package that can be installed side by side because it has a separate namespace.


Thanks for the quick reply! Just to be sure – do I understand it correctly – if I want to replace the actual version with a new one, as I did use the component in a flow, I have to delete the screens / remove the QC component from it?


And to add to this – arrrgh – I just spent 1.5 days finding out a typo in input type field caused the initial error – so no immediate need to upgrade anymore – nevertheless would be helpful to understand whether I would have to delete something before upgrading… And maybe an idea, if feasible, to somehow make the setting field (display mode, input mode) fool proof – a drop-down? Or some input validation… For stupid people like me…

Alex Edelstein

Just posted a new Managed package version of 1.4. It should install and avoid collisions. Give it a try if you’re having trouble installing 1.4

M Hamza

Exactly getting the same issues. Can’t install 1.4 version on sandbox, did try both methods. I hope eric can see this comment.
Although there is another update but only for Summer’20 orgs.

Alex Edelstein

Just posted a new Managed package version of 1.4. It should install and avoid collisions. Give it a try if you’re having trouble installing 1.4

M Hamza

Thanks. Can I install it over unmanaged one?

Last edited 3 months ago by M Hamza Siddiqui
M Hamza

The AppExchange Application or component you have selected is not yet available on your instance of salesforce.com. Please check back in a few days to retry the installation. Press the back button of your browser now and bookmark the AppExchange Directory page so that you can find it later.




Is there any sort of instruction or explanation for this anywhere? Can’t seem to find info on what each field does. I am trying to just set a picklist to a default value from a variable.

Nick Sauer

overrideNext boolean input would be a nice feature, and then on handlechange if that is set true via flow config, you set handleNext navigation and fire that event. I just used this in org, and this was a common request for the visual cards specifically as an expected action. so i just added for our implementation and expect it will be employed frequently.
Thanks for all your work on these things — really learned a ton from them and so many useful bits!

Last edited 3 months ago by Nick Sauer
Alex Edelstein

You seem quite handy with the lwcs, Nick.Want to create a pull request for that extra functionality? You’re not the first who has asked for it.

Shahin M

Hey, is there an easy way to deselect a visual tile once selected? I’m using the visual tiles/cards (fantastic btw), but once I select one, the tile has a blue outline, and when I select another tile then that also receives a blue outline? There’s no way to deselect an outlined box without exiting the flow it seems. Also for others that may be running into a snag when trying to use the Set Component Visibility – I used an AND condition to evaluate the QuickChoice.Value field in order to have subsequent components show/hide. Hope it helps! This is a… Read more »

Last edited 3 months ago by Shahin M

I’m looking for the ability to enforce that a user only select one card (value). Selecting another value should remove the other value.

Chase Kaiser

See parent reply

Chase Kaiser

Do you have a value in the Master Label field? The bug you are describing happens when that field is left null. If you don’t want a title, just hit the spacebar once in that field.


Will the Picklist option work with fields that utilize a Picklist Value Set (Global picklist)?


…update…this does work with Picklist Value sets…

Theo Blagg

Hi All! Great app but I could use some help with a bug I’m seeing. I’m getting the following error when I attempt to assign an output variable (either manually or automatically assigning) to the Quick Choice FSC v1.4 component. Error Message: class java.lang.String cannot be cast to class moduleapi.interaction.FlowPicklistValue (java.lang.String is in module java.base of loader ‘bootstrap’; moduleapi.interaction.FlowPicklistValue is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @1efdcd5) My settings: Display Mode: Picklist Field Name: CurrencyIsoCode Input Mode: Picklist Field Object Name: Opportunity Master Label: Opportunity Currency Value: {!User.DefaultCurrencyIsoCode} Error occurs when I attempt to move to the next screen in… Read more »

Theo Blagg

Little update on this… It looks like it has less to do with the variable output assignment then I originally thought. I’m able to assign an output variable as long as I do not default the input value in the component. I’m currently using  {!User.DefaultCurrencyIsoCode} but have tried other variables and I’m seeing the same issue.

Dub Ashner

What was the final resolution for this? I’m having the same issue. I removed all default values. The error occurs when the values being read in are blank or null.

Niki Vankerk

I’m getting the same type of error but when a different field on the screen hits validation error, like is Required but was left blank, or has validate Input formula that it fails. The fields with validation in my case are just regular Input components.

M Hamza

If anybody don’t wanna use MANAGED one and want to deploy unmanaged, you can use the DEPLOYTOSF button from here
PLUS, Fixed for FSC Mortgage Picklist Values.

Last edited 3 months ago by M Hamza Siddiqui

When “Allow ‘None’ to be Chosen” is set to true and None is selected the value ‘None’ is updated to the defined field instead of a ‘Null’ value (See screenshot). Is this a bug or a missing setting? 😉


Is there an update for this? Love the idea of including a None selection, ,but need it to be an empty string, not the value “None.” Any update?


Why not just create a text formula like IF(FIELD_NAME.value = “None”, null, FIELD_NAME.value) and use it it to update your field instead of using the value directly?


Just for convenience — it’s one less formula to make : )

Quick follow up question:

  • Would your formula work? Or would it instead need to look like this:

IF(FIELD_NAME.value = “None”, null, FieldScreenComponent)

My understanding is that we can’t look to the value of the field name, as it’s only been selected within the Flow, and not assigned as the actual value. Instead, we’d use an Assignment to assign the field the value of either null or what the selection in the screen component via the formula above. Is that right?


Chase Kaiser

My bad, FIELD_NAME was referring to the QuickChoice Component not the field being updated. So if you were updating the field weekday__c with the value of QC_Weekday, your formula would be:

f_strWeekday =
IF({!QC_Weekday.value} = “None”, null, {!QC_Weeday.value})

Then you would update weekday__c = f_strWeekday


Can visual card mode allow only once value to be selected? I’m using card mode for navigation in a flow and the use should only be allowed to select one value.

Andrew Mishler

Awesome component. One question – where do I go to see the icons available in Setup? If I want to add more icons for the visual cards, how do I do that?

Andrew Mishler

Nevermind, I’m seeing now with the Icon page you linked to it’s just built into the API.


Is there a way to add more space around the component? I’m using picklist for the input mode and the field underneath is crowded just under the quick choice field.

Chase Kaiser

You can add “padding-bottom: 10px;” to the css (as the component is unmanaged), or you can add a display text screen component consisting of a single carriage return between quick choice and the field below

[…] For this reason, we turn to an Unmanaged Package called quickChoiceFSC.  […]

Bruce Perry

I’m using Quick Choice 1.4 to present a pick list that depends on record type. That part is working fine. I thought I would see the user’s selection in the variable specified in the Value box. I defined that as


I’m not sure why that doesn’t get filled in. I do see the value if I look in


Goal_Type_rct is the API name of the Quick Choice component.

Does it matter that Commitment_Type is also used in the Value field for a component that is hidden for the case I’m currently testing?


I’m using the .selectedLabel from a Quick Choice FSC v1.4 component, in the Set Component Visibility section of another component. This works in Debug, but when the flow is activated the component visibility doesn’t work. The API value and field value are different in the Picklist. Anyone else experience this?

Funny boy

Can you just have easier example of linking picklist based on picklist field? I have been looking for a few hours but it doesn’t display at all.


I love this component. Thanks! I’m now trying to use it with a dependent picklist field. Is that possible? It doesn’t seem to be respecting the dependency in my screen flow.


I am also having the same issue. Did you find a solution for that?

Paul Carass

Hey Eric,
I have added some custom .jpgs to the Quick Choice Images static resource and replaced the file. But I am struggling to reference them in V2.0.
I’m not seeing any options to reference them.
I use a text string collection variable and add the filename.extension (gate.jpg) as it appears in the static resource and then used this in the Icons Collection thinking it would pick up on them, but no luck.
Where am i going wrong with this?

Chase Kaiser

Make sure your syntax is correct using this currently working flow as a reference. Note: the static resource path is CaSE_SeNsItIvE, including the extension (ex. Quickchoice_Images/hello.jpg != Quickchoice_Images/hello.JPG)

Siri Deva

I just installed the managed package into a sandbox. 1.5 (Beta 1).

When I add the quick choice screen component to my screen, I get the error: “This action references the “c:quickChoiceCpe” lightning web component, which can’t be found”

Any thoughts?

Alex Edelstein

Try the new 2.1 version above. Note that it requires the Flow Base Components library to be installed first.

Heath Parks

I installed v1.4 managed and it loaded into my sandbox, but when I select the quickchoice screen, I am getting an error that states the following “This action references the “c:quickChoiceCpe” lightning web component, which can’t be found.”

how can I fix that?

Alex Edelstein

Try the new 2.1 version above. Note that it requires the Flow Base Components library to be installed first.

Jingli Hu

I just installed version 2.0, but didn’t see the Apex action- get layout id. any ideas?

John M

@alex edelstein
Despite having multiple text collection variables, the object picker does not recognize that any exist. And when I enter the correct name of a text collection var, the control still complains that a valid one is not set:

qcChoices (Screen Component) – The input parameter “Choice Values (String Collection)” can accept multiple values, so the assigned value must be a flow variable with the isCollection property set to true.

Quick Choice behavior.png
Brian Doogan

John I just had the same problem. Upgrading flow base components to the newest version (1.2.3 I think) resolved it. https://unofficialsf.com/introducing-flowbasecomponents/

Charity Hardy

I’m not seeing a help text attribute, am i missing something?

Vijay K

Is this component supports the OOB set visibility functionality when the controlling field changes ? The initial happy path is working fine, but when take a negative condition (hide the field) then click next screen and come back to previous screen and change the controlling filed to render the next component not working. Assigning the Object Name/Filed Name as ‘undefined’ not resetting the values, keeping the original values in the initial path.


Is there a way to change the font size or type. Trying to match with other text box items for community cloud


Has anyone had luck using the QuickChoice component in mobile? I just tried, and scrolling through the picklist values isn’t working.


Hey everyone, how are people getting a list of Picklist values into the card view option? My first guess was to add the values as a string collection, but then how do I match up the values and labels? And additionally, I’d love if there was a more dynamic way to update the collection with the picklist values (I’m just hardcoding it right now to the actual values).

Last edited 1 month ago by Atticus
Giang Nguyen

After trying all different types of input into the component, somehow the Quick Choice component is not visible to me in the screen flow as an admin or end user. I am just trying to display the standard Industry picklist field on the Lead object which should not be required and takes record types into consideration. I have filled in all the necessary fields according to the guide. Does somehow know how to fix this?


I have QuickChoice FSC v2.0 installed. I’m unable to install QuickChoice CPE v2.1 due to the following error: Your request to install package “quickChoiceCPE ver 0.1” was unsuccessful. None of the data or setup information in your salesforce.com organization was affected.Cannot add component of type:StaticResource named:Quickchoice_Images subjectId:081m00000005Lvc to another package because it is an installed component.package.xml: Cannot add component of type:StaticResource named:Quickchoice_Images subjectId:081m00000005Lvc to another package because it is an installed component. I tried just manually deleting the ‘Quickchoice_Images’ static resource, but as it is used by the QuickChoice FSC package, it can’t be deleted. Do I need to remove… Read more »

Eric Smith

Gary, There was a packaging issue that causes v2.0 to not be directly updatable to a later release. This should not be an issue in the future once v2.1 or greater is installed. Your best bet will be to uninstall v2.0. Since you have some Flows already using that version, you will need to remove (delete) them first. Don’t despair as you have some options available to help with that. You might get a message like this, “Unable to uninstall package” followed by one or more “Component is in use by another component in your organization. My_Flowname“. You will need… Read more »

Chase Kaiser

Thanks for this component Eric, it’s been a game changer for us! One request if I may, how difficult would it be to add a boolean attribute that when checked, would essentially allow the visual cards to be treated as buttons by auto-navigating NEXT upon selection? I have several flows where I use QC cards to quickly navigate through decision trees and allowing the user to select + next with one click would tremendously speed up the process, especially for those that are used dozens of times a day. Ex. Clock In/Out Screen Flow: QC: Clocking in or out? >… Read more »


You can do this with some simple changes. Just add a FlowNavigationNextEvent at the end of the handleChange(Event) function in the controlller.

Make the execution depended on a new input variable, that you have to add to the Component and the CPE. Also consider, that a quickChoice component on the last screen of a flow may need a FlowNavigationFinishEvent.

So it might be better to use a string input variable that can either be empty, next or finish.


Chase Kaiser

Thanks for the quick reply Clifford. Unfortunately, I am not yet to the point where I am skilled enough to work with LWCs. I am relatively late to the salesforce game and just started getting a handle on aura when everyone here switched to lightning. Hopefully I will get there soon and if so, will certainly issue a pull request with the add functionality to share, I was just hoping it might be an easy change that could be included in the next release so I could use it in my current build.

[…] this page for the most recent install […]

Carl Bussema

I installed the base components 1.2.5, this component (2.2) and a different component from this site (Convert CSV to records) and i have THAT action, but not the ones here like Get Record Type Info. I do have the new components in my Flow Builder, including Quick Choice FSV.

Last edited 26 days ago by Carl Bussema
Wilson Wong

Is anyone else having this bug where you can select multiple visual cards? I have download the latest version for both the quick choice and the base component

Screen Shot 2020-09-11 at 12.41.05 PM.png

You can get around this by making one change to the code, just change the input type to checkbox-button and it will let you select and deselect. at least it worked for me. it doesnt add the blue check box but still highlights the selection and im sure you could tweak the code to put the blue checkbox back

Dan C

I installed this package and set up the basics using a picklist to make a choice. I want to use visual cards. I cannot seem to get the recordTypeID to pass into my recordDetail FSC component when using visual picker. Working fine using picklist. Any pointers?

Kenny Barry

Maybe I’m missing it, but can you direct me to the link to install the current & latest version (2.3)?

Alex Edelstein

it’s there now


Hi, is Account Contact Relationship object supported? I can’t find it while choosing object in picklist field mode.

Russell Millican

Hi Alex, love this solution. Working great to prepopulate picklist values with default. But I’m encountering an error in a scenario with component visibility. One quickchoice component controls the visibility of two others below it and when a user first interacts with the questions, all works fine, but if the controlling field is set to the value that hides the other two questions, and a user goes to another screen but returns to this one, the other two questions will no longer appear, even though a display text field just above them will with will – with the same conditional… Read more »

Last edited 11 days ago by Russell Millican
Alex Edelstein

this problem is probably related to how Next and Previous work with lightning components. Tricky area that we’re working on. this may help https://unofficialsf.com/optimizing-lightning-component-inputs-and-outputs-in-flow-screens/

Tom Connolly

I am having a hard time Updating the “Add a “None” choice” to false. I make the change, save it and then debug and it evaluates true still? If I delete the component and set it back up again without ever flagging it true it works great. small bug. great tool so far! Huge time saver.

Last edited 8 days ago by Tom Connolly
Kenny Barry

I’m only able to select String fields from a record variable when specifying a default value for a picklist or radio button group.

Is this a limitation or is there a way to make picklist fields available that I’m missing? Any help is much appreciated.

[…] Learn more here. […]