Ann Droppers - 5 months ago
I agree that this needs to be fixed. But check out https://unofficialsf.com/quick-choice-improved-picklists-and-radio-buttons-for-flow/ for a great workaround.
Brendan Sheppard - 5 months ago
Why in flow builder does it list 'No default Value' as an option for a picklist and also show --None-- in the 'Edit Screen' as an exmaple yet in real life not allow it? Seems like part of the frustration is not just not allowing this functionlityt but also having poor UI that gives us the impression this is something that can be done when it cannot?
Aleksandar Basic - 5 months ago
Thank you so much. This is a great workaround.
Side note - the populated values in all the fields are wiped after the if contition that fires the error. If you want them saved, you must create a variable for each and store it prior to the loop and give each field a default value of their variable.
Cassie Chen - 5 months ago
Issue #2 is a huge pain point!
Users can easily miss updating a picklist field during the flow if it defaults to the first value. I also don't like the idea of adding NONE as a new value in the field. It doesn't add any value to the field and don't want users to abuse using the NONE value!
Marcel Oesterhaus - 6 months ago
Your post gave me the right idea, but in the end I solved it without the need of an extra screen component throwing an error. Instead you can do the following to solve this: