John Sadler - 8 months ago
Similar problem except I want my Users to see the Current Picklist value in their opportunity in the Screen. If it's not what they need, then they choose from the list and this passes back into the opportunity.
Problem with the Default is that I can end up with a whole bunch of picklist values incorrectly changed.
So far my only solution is to create a Choice called Existing Value (=the value in the opportunity) as the Default and under the picklilst I show the existing value from the Opportunity in a Text field (same solution as others have come up with I think)
I thought I may have been missing something but apparently not :-)
Not the first time Salesforce have promised me so much and then failed to get all the way to the finish line.
Andy Rouse - 9 months ago
In each of our flows that have picklists that need to be required (but cannot have a default value), we need to build in an extra decision component and loop-back in order to validate that the picklists and navigate the user back to the page. This is unecessarily complicated and a poor user experience. Flow is so close to being powerful and applicable in lots of situations, but it's all of these weird behaviours that mean it's easier for coders to stick with code.